linux/poky.git/bitbake/lib/bb/cooker.py, branch 1.7_M3

bitbake: cooker: tweak CookerCollectFiles::find_bbfiles

2014-08-23T22:02:00+00:00

since python-2.5 string.endswith() takes a tuple (Bitbake rev: 86a67a1fd4244da9343dbf14deed1ad0d3003f32) Signed-off-by: Bernhard Reutner-Fischer Signed-off-by: Richard Purdie

bitbake: cooker: Get rid of duplicate 'import re'

2014-08-02T08:57:11+00:00

The re module was imported at the top, no need to do it again. (Bitbake rev: c29c2370635075949c75937c237602600f4f10dc) Signed-off-by: Namhyung Kim Signed-off-by: Richard Purdie

bitbake: "per-package" should say "per-recipe"

2014-07-23T09:02:13+00:00

(Bitbake rev: 1cd369883469747a8158826bb8d67dcca2a8577f) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie

bitbake: cooker: Overwrite IMAGE_BASENAME to default in custom image

2014-04-04T14:08:26+00:00

This solves a problem of custom images which inherit a base image with IMAGE_BASENAME overwritten in their recipe by a different value than its default one: ${PN}. The value of IMAGE_BASE causes a crash when hob will try to create symbolic links to the resulting images from the deploy directory, because it will look for names similar to -edited-timestamp-machine.rootfs.* which might be different from the actual resulting image. The solution is to simply overwrite IMAGE_BASENAME in the custom recipe to the default value in the case IMAGE_BASENAME is found in the base recipe. Some recipes which were affected by this problem are those from meta-fsl-demos (e.g.: fsl-image-test). [YOCTO #6017] (Bitbake rev: e42ee93519000f827be49659b6b5fb7717b3d592) Signed-off-by: Marius Avram Signed-off-by: Richard Purdie

bitbake: bitbake: cooker: mark setFeatures command as read-only

2014-04-01T11:53:26+00:00

This patch makes sure that the setFeatures command is marked as read-only and that it can only run if the cooker is in the initial state. Additionally, remove logging from the XMLRPC module in favor of sending the exception to the client for easy processing. [YOCTO #6089] (Bitbake rev: f0a1a3e24757f7658d272035620465f92a3e4c3c) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: bin/bitbake/cooker: Ensure initial featureset is optimal

2014-03-30T09:10:36+00:00

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. (Bitbake rev: 1249543c4dbf3edeac033d888497864cfc807a4e) Signed-off-by: Richard Purdie

bitbake: cooker: Only change self.data if it exists

2014-03-30T09:10:36+00:00

With the change to more optimal default featureset behaviour, a race was exposed by hob where the code may try and change self.data before it exists. This change avoids that. When the datastore is created, the cooker configuration is used so data tracking is correctly handled regardless. (Bitbake rev: 9d8f7efbc39d64124936ccaeb3c47a112e595d78) Signed-off-by: Richard Purdie

bitbake: cooker/event: Overhaul sanity test mechanism

2014-03-27T09:42:08+00:00

Sanity tests are currently a pain as its hard to control when they run. This results in issues where for example the bitbake -e output is not useful as the sanity tests prevent it from executing. The sanity tests should run later than the base configuration. This patch changes the sanity tests to always be event triggered with the option of returning either events on the status, or raising errors. A new cooker feature is used to change the behaviour depending on the controlling UI. This does need a change to sanity.bbclass in the OE metadata but its worth the pain for the increased flexibility and control this offers UIs and the improvement to the user experience. (Bitbake rev: 32e171bcc92c6e27fefee971e8714ddf8e1a8ac1) Signed-off-by: Richard Purdie

bitbake: cooker: delVar in removeConfigurationVar

2014-03-25T13:26:54+00:00

When a variable was removed from a configuration file it was not removed from memory. This also had the effect of not allowing to set a new value for the same variable with saveConfigurationVar. (Bitbake rev: 30cd1fab6633aaf50ef53eefccc6d69d598eb293) Signed-off-by: Marius Avram Signed-off-by: Richard Purdie

bitbake: bitbake: cooker: some IMAGE_FEATURES not recognized

2014-03-14T14:25:40+00:00

Fixes an issue in hob which happened when the local.conf file was modified externally by appending "eclipse-debug" to the IMAGE_FEATURES variable. The reason of the problem is that some IMAGE_FEATURES are not available in the image.bbclass file and they are declared in the core-image.bbclass. Now a default hob image will inherit core-image. [YOCTO #5711] (Bitbake rev: 81413d94f40f58d790d7a7dc4259108f9c5d4fc0) Signed-off-by: Marius Avram Signed-off-by: Richard Purdie