summaryrefslogtreecommitdiff
path: root/bitbake/bin
Commit message (Collapse)AuthorAgeFilesLines
* bitbake-layers: fix bug with env vars leaking inChris Larson2011-02-101-0/+1
| | | | | | | | | | I forgot that bin/bitbake is what does the environment filtering based upon BB_ENV_WHITELIST, etc. (Bitbake rev: 2cc6b6951bd17832866ec710029d119d2df31ba4) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add initial bitbake-layers scriptChris Larson2011-02-101-0/+153
| | | | | | | | | | | | | | | | | This script has subcommands which operate against your bitbake layers, either displaying useful information, or acting against them. Currently, it only provides a show_appends command, which shows you what bbappends are in effect, and warns you if you have appends which are not being utilized. Currently, a bug exists when using this due to the DataContext stuff, but I'm not certain as to the root cause, it appears to be the bb package relying implicitly on the way the bitbake script does things. A fix for that issue will be forthcoming, as will further subcommands. (Bitbake rev: 78b6d4cb26cec3321f8eec9889205a6b93b2ee18) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-swab: Convert to attach strace to the process to obtain the required ↵Richard Purdie2011-02-101-8/+0
| | | | | | swabber data Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Resurrect alternative UIsBob Foerster2011-01-051-1/+1
| | | | | | | | | | | | | | | | The various alternative UIs have been updated to once again be functional with the latest bitbake internals. Each of the UIs still have much room for functional improvement. In particular, they have been updated to: - interact with the new process based server - handle the current set of events and notifications fired from the server and its associated subsystems (Bitbake rev: b947e7aa405966262c0614cae02e7978ec637095) Signed-off-by: Bob Foerster <robert@erafx.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Ensure that the invalid UI error goes to stderrChris Larson2011-01-041-11/+20
| | | | | | | (Bitbake rev: 76aeea2c23a518046d0b26f1a6fc43287a180a9d) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Silence python 2.7 nested context manager warningChris Larson2011-01-041-0/+1
| | | | | | | (Bitbake rev: 1c38f19fb8da2e6c55394162d0142e7146387e54) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Kill the uncaught exception handlerChris Larson2011-01-041-12/+6
| | | | | | | | | | | | We now wrap the main() in a try/except, ensuring that both the main portion of bin/bitbake and the UI raising an exception will be shown to the user. For the server and workers, we can ensure in the server itself that exceptions are handled correctly. (Bitbake rev: 240d4a7ae80a6636c302ae84266ddfed7a7fcedd) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Rename the ui 'init' method to 'main'Chris Larson2011-01-041-16/+5
| | | | | | | | | | As these may run the UI in a blocking fashion and then return the exit code, 'init' was an inappropriate name, and 'main' is more appropriate. (Bitbake rev: 4d081a0ed759bd526ab01849d650bd9e8d80ddd1) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Error more pleasantly when trying to use python2.4Chris Larson2011-01-041-10/+11
| | | | | | | (Bitbake rev: 57402ee727c8c1d8f5017534fb0f5e0b20aaaa5b) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Don't show a traceback for a python version errorChris Larson2011-01-041-1/+4
| | | | | | | (Bitbake rev: 44c325306e55336b7b416fd88b39874012a3f603) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Use __file__, not sys.argv[0]Chris Larson2011-01-042-2/+2
| | | | | | | (Bitbake rev: 97e92abe49663eee189c89c1dc91fe69891faf73) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Don't show uncaught exception message for KeyboardInterruptChris Larson2011-01-041-1/+5
| | | | | | | (Bitbake rev: 29634acd262b06fd14f6ef1e134346f274cf448f) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Switch bitbake internals to use logging directly rather than bb.msgChris Larson2011-01-041-6/+6
| | | | | | | | | | | | | | We use a custom Logger subclass for our loggers This logger provides: - 'debug' method which accepts a debug level - 'plain' method which bypasses log formatting - 'verbose' method which is more detail than info, but less than debug (Bitbake rev: 3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Use logging in the knotty ui, and pass the log record across directlyChris Larson2011-01-041-1/+4
| | | | | | | | | | | | | | | | | | This kills firing of Msg* events in favor of just passing along LogRecord objects. These objects hold more than just level and message, but can also have exception information, so the UI can decide what to do with that. As an aside, when using the 'none' server, this results in the log messages in the server being displayed directly via the logging module and the UI's handler, rather than going through the server's event queue. As a result of doing it this way, we have to override the event handlers of the base logger when spawning a worker process, to ensure they log via events rather than directly. (Bitbake rev: c23c015cf8af1868faf293b19b80a5faf7e736a5) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Use the python logging module under the hood for bb.msgChris Larson2011-01-041-2/+5
| | | | | | | (Bitbake rev: 47ca82397bc395b598c6b68b24cdee9e0d8a76d8) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Ignore python warnings that come from places we don't care aboutChris Larson2011-01-041-1/+5
| | | | | | | | | Only shows warnings that come from bb, oe, or <string> (Bitbake rev: 57018687f60b222ab220dd904c4bf870780171e9) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Drop the 'ui failed to start' message, as the ui_init does more in knottyChris Larson2011-01-041-5/+1
| | | | | | | (Bitbake rev: 39087138ffd5d427f07ecaa580a40885c5ffaff3) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake/bitbake-runtask: Since the parent has set the environment up cleanly ↵Richard Purdie2010-12-101-2/+2
| | | | | | we don't need to filter this ourselves anymore Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Overhaul environment handlingRichard Purdie2010-12-091-0/+3
| | | | | | | | | | | | | | Currently, anything whitelisted in the environment makes it into the worker processes. This is undesireable and the worker environment should be as clean as possible. This patch adapts bitbake sosme variables are loaded into bitbake's datastore but not exported by default. Any variable can be exported by setting its export flag. Currently, this code only finalises the environment in he worker as doing so in the server means variables are unavailable in the worker. If we switch back to fork() calls instead of exec() this code will need revisting. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake-runtask-strace: simple shell script to wrap tasks in a strace callJoshua Lock2010-11-141-0/+8
| | | | Signed-off-by: Joshua Lock <josh@linux.intel.com>
* bitbake: Rewrite profiling code so its functional for both none and xmlrpc ↵Richard Purdie2010-11-131-2/+2
| | | | | | backends Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake-runtask: Ensure logging settings take effect in the worker process ↵Richard Purdie2010-10-141-1/+4
| | | | | | (and pass verbose setting) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake-runtask: Ensure logging options are inherited from the parentRichard Purdie2010-10-111-7/+12
| | | | | | [BUGID #291] Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake/bitbake-sigdiff: Extend to handle dumping single state siginfo filesRichard Purdie2010-09-301-1/+4
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake/bitbake-runtask: Signatures are needed in task context and have ↵Richard Purdie2010-09-291-0/+1
| | | | | | little overhead so enable in worker context Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Pass task hash information to subprocessesRichard Purdie2010-09-281-3/+20
| | | | | | | Pass task has informaiton to work processes, allowing full manipulation of the hash data in the task context allowing checksums to be usable. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake/build.py: Set BB_FILENAME to represent the .bb file being built ↵Richard Purdie2010-09-131-1/+1
| | | | | | (including any virtual prefix) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: save the initial PATH for use when starting a subprocessJoshua Lock2010-09-081-0/+1
| | | | | | | | | | | It was possible for bitbake-runtime to be run against a semi-installed python-native resulting in tracebacks with ImportError's. To prevent this we stash the initial PATH in the BBConfiguration when bitbake is started and then set this in the env when launching bitbake-runtask through subprocesses Popen() call. Signed-off-by: Joshua Lock <josh@linux.intel.com>
* bitbake/bitbake-runtask: Ensure signals to the parent don't pass to the ↵Richard Purdie2010-09-071-0/+7
| | | | | | children directly Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Add missing signature filesRichard Purdie2010-09-031-0/+9
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Implement signaturesRichard Purdie2010-09-031-0/+3
| | | | | | Includes functionality to find out what changes between two different singature data dumps. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Correctly route events from the worker to the serverRichard Purdie2010-08-201-5/+12
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Switch to use subprocess for forking tasks and FAKEROOTENV to run ↵Richard Purdie2010-08-191-0/+77
| | | | | | shell and python under a fakeroot environment Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* *: use print() as a functionBernhard Reutner-Fischer2010-07-161-3/+3
| | | | | | | | | to make python3 happy (Bitbake rev: c82926ccdd4ec4e3ad6e78a381dacb96adf9b409) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Apply some 2to3 refactoringsChris Larson2010-07-022-15/+13
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Until the interactive mode is fixed, kill it from the valid options, to ↵Chris Larson2010-07-021-3/+0
| | | | | | | | | avoid confusion (Bitbake rev: 65a51bb20677148a29b9e472f6d9d0a97798f024) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Move serverConnection.terminate() back into the finallyChris Larson2010-07-021-1/+2
| | | | | | | (Bitbake rev: 58e1b0a5dbd0f1ca137ad7ed1bd7ad9975a20fb7) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Limit the traceback length in the default exception handlerChris Larson2010-07-021-1/+1
| | | | | | | (Bitbake rev: 2b9dc5b55e24b4946ff03bf30ca52a48547caaad) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Resurrect the excepthook, this time just sending the info with bb.fatalChris Larson2010-07-021-0/+8
| | | | | | | (Bitbake rev: 07757a1bf1129cc6a967a7cf1815d3d46a6bbdcf) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* remove return in finally statementCliff Brake2010-07-021-3/+3
| | | | | | | | | | causes exceptions to not be handled after the finally statement (Bitbake rev: 1a04610dea376340b9ea4c109f64995b4fd6ad02) Signed-off-by: Cliff Brake <cbrake@bec-systems.com> Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Drop the non-debug traceback suppressor, at this point I think it does more ↵Chris Larson2010-07-021-13/+0
| | | | | | | | | harm than good (Bitbake rev: 2c66ddc2713061ba31363ea69c24944f4a7cd3a8) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Reorganize the main exception handling so an attribute exception raised in ↵Chris Larson2010-07-021-5/+8
| | | | | | | | | the ui isn't misinterpreted (Bitbake rev: 49b8bab706c59e93287f8540187b62ba3ece0a11) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Adjust the exception handling based on Cliff Brake's patchChris Larson2010-07-021-1/+2
| | | | | | | | | | Rather than printing the exception ourselves, might as well re-raise and let the default exception handler do it for us. (Bitbake rev: acca7eb8450cbe30d65b5b266f1a642e7965df8a) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Fix the debug level check in print_exceptionChris Larson2010-07-021-1/+1
| | | | | | | (Bitbake rev: 9cb52edf9198fe6db735abbb61d0c4026c97a8d9) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Move the python version check into the python packageChris Larson2010-07-021-5/+1
| | | | | | | | | | | | | | | This ensures the check is run for anyone using the package, including setup.py, though it's sad that it's necessary, since all it really wants is __version__. Ideally, we'd avoid the version check entirely in favor of checking for functionality, but that's rather difficult with language constructs like context managers, so this'll do for now. (Bitbake rev: f936f1c0edf70860ea0f39ec1a500ba43b56f289) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Drop an unnecessary second python version check and use the less ugly ↵Chris Larson2010-07-021-6/+2
| | | | | | | | | sys.version_info (Bitbake rev: 8f4b7b10f8740a41c085beeca5105f15204b0979) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Bump version to 1.11.0Chris Larson2010-07-021-1/+1
| | | | | | | (Bitbake rev: 6c89c332664a7789d02a701e7e530838ab778264) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Move the python version check before the module imports, in case the modules ↵Chris Larson2010-07-021-4/+7
| | | | | | | | | utilize the newer python features (Bitbake rev: 87c15dfcbeb10e7cafb14726209e4954671b3dbe) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Ignore deprecation warnings for nowChris Larson2010-07-021-0/+1
| | | | | | | (Bitbake rev: 661fe59445161c5bc6a2e73b7fcbf9d20c492e27) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Import fixupsChris Larson2010-07-021-1/+1
| | | | | | | (Bitbake rev: 4fa052f426e3205ebace713eaa22deddc0420e8a) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3 (git 2.46.0) at 2024-11-15 19:56:50 +0000