summaryrefslogtreecommitdiffstats
path: root/bin/bitbake
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: Update version to 1.33.1Richard Purdie2017-02-071-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Bump version to 1.33.0 (develoment version)Richard Purdie2017-01-271-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update version to 1.32.0Richard Purdie2016-10-111-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update version to 1.31.2Richard Purdie2016-10-051-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update version to 1.31.1Richard Purdie2016-08-181-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Convert to python 3Richard Purdie2016-06-011-1/+4
| | | | | | | Various misc changes to convert bitbake to python3 which don't warrant separation into separate commits. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Switch to post release versionRichard Purdie2016-04-291-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Update version to 1.30.0Richard Purdie2016-04-061-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Bump version to 1.29.1Richard Purdie2016-03-301-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Bump version post release to 1.29.0Richard Purdie2016-02-121-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/lib: Update version to 1.28.0Richard Purdie2015-10-011-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Bump version to 1.27.1Richard Purdie2015-06-091-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: use sys.exit to simplify the codeEd Bartosh2015-04-281-8/+5
| | | | | | | | | Used sys.exit instead of assigning exit code to variable. This way it's more clear when bitbake exists and which exit code is used. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Check if bitbake versions matchEd Bartosh2015-04-281-0/+4
| | | | | | | | | | | | | | Bitbake program and core versions must match. Moved __version__ from main.py back to bin/bitbake. Implemented check for version match in bin/bitbake. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> tbs Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Handle BBMainExceptionEd Bartosh2015-04-281-1/+4
| | | | | | | | | | | | | | Some error messages were lost because BBMainException was inherited from bb.BBHandledException. When bb.BBHandledException is processed error messages are not printed as they suppose to be printed before raising this exception. Stopped to inherit BBMainException from bb.BBHandledException. Handled BBMainException in bin/bitbake and printed error message to the stderr. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: Create bitbake_main APIEd Bartosh2015-03-241-357/+6
| | | | | | | | Moved most of functionality of bin/bitbake to lib/bb/main.py to be able to call bitbake from python code. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: only check that /dev/shm is writable on LinuxRoss Burton2015-01-211-2/+2
| | | | | Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* add option to write offline event log fileAlexandru DAMIAN2014-12-121-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | This patch adds a "-w/--write-log" option to bitbake that writes an event log file for the current build. The name of the file is passed as a parameter to the "-w" argument. If the parameter is the empty string '', the file name is generated in the form bitbake_eventlog_DATE.json, where DATE is the current date and time, with second precision. The "-w" option can also be supplied as the BBEVENTLOG environment variable. We add a script, toater-eventreplay, that reads an event log file and loads the data into a Toaster database, creating a build entry. We modify the toasterui to fix minor issues with reading events from an event log file. Performance impact is undetectable under no-task executed builds. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
* bitbake: Update to 1.25.0 as development version after releaseRichard Purdie2014-12-031-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: clarify startup messageAlexandru DAMIAN2014-10-301-1/+1
| | | | | | | Fix the startup message by making clear which server runs on which port. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
* bin/bitbake: Update to version 1.24.0Richard Purdie2014-09-231-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: Update to version 1.23.2Richard Purdie2014-09-111-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: remove choices for dump-signaturesRobert Yang2014-07-241-1/+1
| | | | | | | The SIGNATURE_HANDLER can be defined by the user, so we can't use choices. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* "per-package" should say "per-recipe"Robert P. J. Day2014-07-231-1/+1
| | | | | Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: update help message for dump-signaturesRobert Yang2014-07-211-2/+2
| | | | | | | | | | | | | | | The bitbake -S had been updated which always reuires an argument, so update the help info: - Add the two args in the help message: none and printdiff - Use type="choice" so that we can get more friendly error messages, for example: bitbake: error: option -S: invalid choice: 'printdiffX' (choose from 'none', 'printdiff') - dump-signatures=DUMP_SIGNATURES -> dump-signatures=SIGNATURE_HANDLER Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xmlrpc: add support for token reusingAlexandru DAMIAN2014-06-121-1/+7
| | | | | | | | | | | | | | | | | We add support to specify a connection token in the command line and in the environment variable BBTOKEN. When a client registers to a bitbake server, that client will have exclusive access to the server. The client is identified by a server-supplied token. If a client terminates, we cannot reconnect to the server as the token is lost. This patch adds the capability to specify the connection token in the command line for xmlrpc clients. This allows us to have bitbake work as an already-authenticated client with the server and resume sending commands to a server. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
* toaster: update toaster to run in managed modeAlexandru DAMIAN2014-06-061-18/+16
| | | | | | | | | | | | We disable bitbake self start to prevent race condition. ToasterUI will shutdown the server when the build is done if running in managed mode. We fix usage of kill server flag in the bitbake binary. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xmlrpc: client - remove fatal errorsAlexandru DAMIAN2014-06-061-10/+13
| | | | | | | | | | | | | | | | | | | When we use the XMLRPC client API to connect to a bitbake server, we want to receive errors from the API instead of having the API exiting without warning. Thus the "bb.fatal" calls have been replaced with "bb.warn" calls, and we re-raise the original exception for handling by the original caller. The bitbake starting script has been modified to properly test for failures in calling the client API and handle them. Additional error handling added in the client, as to prevent fatal crashes. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: move configuration reading codeAlexandru DAMIAN2014-06-061-1/+22
| | | | | | | | | | | | | The configuration reading code should live in the main bitbake entry point, and the server modules should be supplied with correct configuration instead of attempting to parse from configuration files. This patch moves the endpoint address reading from XMLRPC to the bitbake main script. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Bump version to 1.23.1Richard Purdie2014-05-011-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update to version 1.23.0 for masterRichard Purdie2014-04-101-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update to version 1.22.0Richard Purdie2014-04-101-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: Only try and process an event_queue if it existsRichard Purdie2014-03-301-1/+1
| | | | | | | The connection may have failed before the event queue has been setup. Handle this correctly in the exception handler. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake/cooker: Ensure initial featureset is optimalRichard Purdie2014-03-281-7/+9
| | | | | | | | | | | If the featureset didn't match the defaults, we'd pay the price of two base configuration parses which showed up adversely in the performance benchmarks. This also passes the feature set into the cooker creation so in the common case we don't have to reset the server. This speeds up both knotty and hob startup. If the featureset doesn't match, the system will reset as before, this just streamlines the common case. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Force -S option to take a parameterRichard Purdie2014-03-261-2/+2
| | | | | | | | | | | There is no easy way to make this change. We really need parameters for the -S (dump signatures) handling code. Such a parameter can then be used within the codebase to handle the signatures in different ways. For now, "none" is the recommended default and "printdiff" will execute the new (and more expensive) comparison algorithms. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fix typo in variable nameRoss Burton2014-03-111-1/+1
| | | | | | | | When passing -t with an incorrect server type, the error message was using a variable that doesn't exist. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toaster: add two-stage commit startup logicAlexandru DAMIAN2014-01-071-0/+1
| | | | | | | | | | | | | | | Toaster start script lunches multiple process components of the toaster system. This patch adds logic into the startup script to safely fail startup and do proper cleanup on any error that may happen during system start. Bitbake needs to return 0 if it will successfully lunches the server-mode. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Update to version 1.21.1 for masterRichard Purdie2013-12-201-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.lock: Add host:port to bitbake.lock for memres serverJason Wessel2013-12-021-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | The idea is to build on the --status-only option for bitbake and expose a mechanism where the oe init scripts can easily switch between memres server and the non-memres server. In the case of the standard oe init script the following can shut down the server: if [ -z "$BBSERVER" ] && [ -f bitbake.lock ] ; then grep ":" bitbake.lock > /dev/null && BBSERVER=`cat bitbake.lock` bitbake --status-only if [ $? = 0 ] ; then echo "Shutting down bitbake memory resident server with bitbake -m" BBSERVER=`cat bitbake.lock` bitbake -m fi fi A similar function can be used to automatically detect if the server is already running for the oe memres init script. This new functionality allows for the memres init script to be started in a new shell and connect up to an alaready running server without seeing the error of trying to start the server multiple times. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake, xmlrpc.py: Implement memory resident auto port configuration/restartJason Wessel2013-12-021-0/+10
| | | | | | | | | | | | | | | | | | This patch adds the ability to dynamically select a port for the bitbake memory resident server when the BBSERVER port is set to -1. This allows for running multiple instances of the bitbake memory resident server on the same system in different build directories. The client portion of the bitbake instance can also request that the server automatically start when using the auto port feature. This is to deal with a bitbake instance that eventually times out and exits or that has died for some unknown reason. The new functionality allows for lazy startup of the server after sourcing the init script for the memory resident functionality. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Add --status-only optionJason Wessel2013-12-021-1/+14
| | | | | | | | | The --status-only option is purely to check the health of the server. The idea is to use it from the oe environment script so as to know if the server needs to be started or not. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update post 1.20 to development versionRichard Purdie2013-10-141-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: Clarify server error messageRichard Purdie2013-10-041-2/+2
| | | | | | | Getting an error message about --remote-server being set when really BBSERVER was is confusing, clarify the message. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: Clear ui-queue when starting a serverRichard Purdie2013-10-041-0/+1
| | | | | | | | When starting a server we don't want to show the debug event queue which is reserved for when when errors have occurred. This patch copies the UI code to ensure the user doesn't see confusing output. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: No need to show tracebacks for BBHandledExceptionsRichard Purdie2013-10-041-0/+2
| | | | | | | | For BBHandledExceptions, we've already displaced a sensible error to the user so we don't need to do it again. Just exit with an error value. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: Catch establish connection log messagesRichard Purdie2013-10-041-2/+2
| | | | | | | | If for example you try "bitbake -m" with an invalid BBSERVER, error messages are not displayed. This change ensures logging is in place to catch and display such errors. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update to version 1.20.0Richard Purdie2013-09-241-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bin/bitbake: Improve --help textRichard Purdie2013-09-221-30/+29
| | | | | | | | | | | | | | The --help text was rather inconsistent in style and plain incorrect in places, using confusing terminology in others. I guess most people know what the options do and don't read this but its confusing to new users. This updates it to use the terms recipe and task consistently, remove the references to stage, bbread and generally try and make the output more useful. [YOCTO #4856] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker,xmlrpc,servers: implement CookerFeaturesAlexandru DAMIAN2013-09-181-20/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implementing feature set selection that allows a client to enable specific features in the server at connection time. Only enabling of features is supported, as there is no way to safely remove data loaded into the cooker. Once enabled, a feature will remain enabled for the life of the cooker. Client-server connection now supports specifying the feature set required by the client. This is implemented in the Process server using a managed proxy list, so the server cooker will now load dynamically needed features based on what client connects to it. In the XMLRPC server the feature set is requested by using a parameter for registerUIHandler function. This allows observer-only clients to also specify features for the server. The server code configuration now is completly separated from the client code. All hardcoding of client knowledge is removed from the server. The extra_caches is removed as the client can now specify the caches it needs using the feature. The UI modules now need to specify the desired featureSet. HOB is modified to conform to the featureSet specification. The only feature available is CookerFeatures.HOB_EXTRA_CACHES which forces loading the bb.cache_extra:HobRecipeInfo class. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: read BBSERVER environement for remote serverAlexandru DAMIAN2013-06-171-0/+9
| | | | | | | | | This change allows bitbake to connect to a remote server by reading the BBSERVER environment variable and effecting the config. Basically a shortcut to the command line parameters. Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>