summaryrefslogtreecommitdiffstats
path: root/bin/bitbake
AgeCommit message (Collapse)Author
2011-06-09Update version to 1.13.11.13.1Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-09Drop psyco supportRichard Purdie
At best it gave 1-2% improvement now, its 32 bit x86 only and isn't supported after python 2.6. PyPy is probably a better option now. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-08bitbake/server: Move server specific code into the server backend and create ↵Richard Purdie
a server API Move the server implementation specific code into the server backend where it belongs and replace this with a set of object method calls which establish the server, detach it and then connect to it using appropriate IPC. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-08bitbake/server/process: Move implementation knowledge of event queue into ↵Richard Purdie
the server Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-02-18Increment version for development versionRichard Purdie
2011-02-18Release 1.12.01.12.0Richard Purdie
2011-01-10bitbake: handle IOError from event_queue.getChris Larson
These can occur in a particular ^C shutdown, so just break out of the event queue empty loop if we encounter it. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-29Implement task signaturesRichard Purdie
Includes functionality to find out what changes between two different signature data dumps. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-17bin/bitbake: [HACK] Empty ui event queue on shutdownChris Larson
This is a workaround to ensure the user always sees any queued up log messages, even if the UI has shut down without showing them. This is far from ideal. The correct fix is to alter the UIs to shut down more cleanly, ensuring they display any remaining queued up events to the user before they exit. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-17Ensure LogHandler is set up for the server constructionChris Larson
If we add the LogHandler object in the server.main, rather than earlier, any log messages emitted during the construction of the server (and, therefore, during the construction of the cooker) will not be seen. This includes the error(s) which the cooker can emit when parsing the command line. With this, we again see the error if you try to use -g without specifying a recipe to operate against. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-17Resurrect alternative UIsBob Foerster
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 Signed-off-by: Bob Foerster <robert@erafx.com>
2010-12-16Forcibly shut down the server if the UI is terminatedChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-16server: fix interrupt handling for processBob Foerster
SIGINT is now blocked within the server context, thus allowing the UI to fully handle all user interaction. There is no longer a need to check for KeyboardInterrupt Exceptions anywhere within the server context. Signed-off-by: Bob Foerster <robert@erafx.com> Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-16Run the server and UI in separate processesBob Foerster
This uses the python multiprocessing module, both to spawn the server process and for communication between the processes. Signed-off-by: Bob Foerster <robert@erafx.com> Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-13Ensure that the invalid UI error goes to stderrChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-13Silence python 2.7 nested context manager warningChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-10Kill the uncaught exception handlerChris Larson
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. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-09Rename the ui 'init' method to 'main'Chris Larson
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. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-03Error more pleasantly when trying to use python2.4Chris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-12-02Don't show a traceback for a python version errorChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-11-26Use __file__, not sys.argv[0]Chris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-09-09Don't show uncaught exception message for KeyboardInterruptChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-09-03Switch bitbake internals to use logging directly rather than bb.msgChris Larson
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 Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-08-27Use logging in the knotty ui, and pass the log record across directlyChris Larson
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. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-08-27Use the python logging module under the hood for bb.msgChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-08-11Ignore python warnings that come from places we don't care aboutChris Larson
Only shows warnings that come from bb, oe, or <string> Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-08-06Drop the 'ui failed to start' message, as the ui_init does more in knottyChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-07-06*: use print() as a functionBernhard Reutner-Fischer
to make python3 happy Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
2010-07-01create cooker object after cleaning the environmentJeff Dike
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. (From Poky rev: 6418d0492a60ed37d13e1060c2e8c09cd127c450) Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-01Move the logger initialization from cooker to utilsJeff Dike
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. (From Poky rev: f9d7e9e3be89ac9141fb0eb7c71eef5a9a82add9) Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-21Apply some 2to3 refactoringsChris Larson
2010-06-21Until the interactive mode is fixed, kill it from the valid options, to ↵Chris Larson
avoid confusion Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-06-18Move serverConnection.terminate() back into the finallyChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-06-18Limit the traceback length in the default exception handlerChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-06-16Resurrect the excepthook, this time just sending the info with bb.fatalChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-06-15remove return in finally statementCliff Brake
causes exceptions to not be handled after the finally statement Signed-off-by: Cliff Brake <cbrake@bec-systems.com> Signed-off-by: Chris Larson <clarson@kergoth.com>
2010-06-10Drop the non-debug traceback suppressor, at this point I think it does more ↵Chris Larson
harm than good Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-06-08Reorganize the main exception handling so an attribute exception raised in ↵Chris Larson
the ui isn't misinterpreted Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-06-04Adjust the exception handling based on Cliff Brake's patchChris Larson
Rather than printing the exception ourselves, might as well re-raise and let the default exception handler do it for us. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-20Fix the debug level check in print_exceptionChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-15Move the python version check into the python packageChris Larson
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. Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-15Drop an unnecessary second python version check and use the less ugly ↵Chris Larson
sys.version_info Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-15Bump version to 1.11.0Chris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-15Move the python version check before the module imports, in case the modules ↵Chris Larson
utilize the newer python features Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-10Ignore deprecation warnings for nowChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-09Import fixupsChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-09Formatting cleanupsChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-09Bump minimum python version check to 2.6.Chris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-09Display python warnings via bb.msgChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
2010-04-09Use __import__ for the ui rather than execChris Larson
Signed-off-by: Chris Larson <chris_larson@mentor.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-24 02:49:10 +0000