summaryrefslogtreecommitdiffstats
path: root/bitbake/bin/bitbake
Commit message (Collapse)AuthorAgeFilesLines
* 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-041-1/+1
| | | | | | | (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: 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: 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: 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>
* *: 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-021-1/+1
| | | | 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>
* Formatting cleanupsChris Larson2010-07-021-47/+51
| | | | | | | (Bitbake rev: 2caf134b43a44dad30af4fbe33033b3c58deee57) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Bump minimum python version check to 2.6.Chris Larson2010-07-021-2/+2
| | | | | | | (Bitbake rev: 85c000cc7db47cfd489cf282c58db2dab0d87908) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Display python warnings via bb.msgChris Larson2010-07-021-2/+18
| | | | | | | (Bitbake rev: 648415a562d92109c4945cb3cc98ed2ec44667a7) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Use __import__ for the ui rather than execChris Larson2010-07-021-6/+6
| | | | | | | (Bitbake rev: 7d00bab300961431f9960cf6759966f608580bc0) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Initialize pkgs_to_build in the BBConfiguration constructorChris Larson2010-07-021-1/+1
| | | | | | | (Bitbake rev: 69a3e4895b88110fd3a25167aa16cf7c00463175) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: create cooker object after cleaning the environmentJeff Dike2010-06-291-2/+2
| | | | | | | | | | | | Previously, the cooker object was created before the environment was cleaned, saving everything that was in the environment and dumping into the run scripts. The patch ensures that the cooker gets a cleaned environment when it's created. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Move the logger initialization from cooker to utilsJeff Dike2010-06-291-0/+3
| | | | | | | | | | | | | | In order to move the environment cleaning, which wants to log a message, before cooker creation, the logging facility initialization needs to happen earlier. So, it is now in init_logger in utils.py and called from bitbake before the creation of the data object. It also seems more correct to initialize a global facility like this from a more global context than the creation of an object, of which there could theoretically be many. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Don't import xmlrpc server unless neededRichard Purdie2010-01-221-1/+2
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bin/bitbake: Add import serverRichard Purdie2010-01-221-0/+1
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Fix UI failure exception handling with python 2.6Richard Purdie2010-01-211-1/+1
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Switch to bitbake-dev version (bitbake master upstream)Richard Purdie2010-01-201-24/+73
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Add a --revisions-changed commandline option to indicate when ↵Richard Purdie2009-07-291-0/+3
| | | | | | floating srcrevs have changed Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Sync with upstream after 2.8.12 releaseRichard Purdie2009-01-021-1/+1
|
* bitbake: Add tryaltconfigs option to disable the alternative configuration ↵Richard Purdie2008-10-281-0/+3
| | | | attempts and make the 'continue' more aggresive
* bitbake: Refactor the environment variable handlingRobert Bradford2008-10-171-9/+3
| | | | | | | Refactor the environment variable handling so that it more closes matches the changes that have been made in bitbake-dev. git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5527 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake/bitbake-dev: Allow much better control of which variable influence ↵Richard Purdie2008-09-301-0/+10
| | | | | | bitbake from the environment git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5347 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake/bitbake-dev: Sync with upstreamRichard Purdie2008-09-301-0/+2
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5346 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Update to 1.8.10 releaseRichard Purdie2008-01-201-1/+1
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@3555 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bin/bitbake: Fix help typoRichard Purdie2007-11-161-1/+1
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@3184 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Sync with 1.8.8 releaseRichard Purdie2007-08-201-1/+1
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@2513 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Sync with upstreamRichard Purdie2007-08-111-1/+18
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@2480 311d38ba-8fff-0310-9ca6-ca027cbcb966