linux/poky.git/bitbake/bin, branch 1.1_M4

Ensure only the filtered environment variables are inherited from the OS

2011-08-15T08:49:37+00:00

The recent change which modified inheritFromOS to use the intial environment, rather than the current environment, introduced a bug such that variables which had been cleaned from the environment where still set in the data store. This patch changes things such that a list of approved environment variables is saved after the environment is cleaned and only the variables in this list are inherited in inheritFromOS. CC: James Limbouris CC: Chris Larson (Bitbake rev: cb6c07054e8baf94614713ec257c643b22266d75) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

bitbake-layers: extend show_layers

2011-08-15T08:49:11+00:00

Make show_layers print layer name, path, and priority in a simple table rather than just the value of BBLAYERS. (Bitbake rev: 29afbf10c00b5ccdd8d2c063dda3f3e2b6aa1624) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake-layers: use logger.plain instead of info

2011-08-15T08:49:11+00:00

The INFO: prefix makes sense in bitbake itself but in bitbake-layers is just noise. Changing this exposed the fact that the logger was not being set up correctly (which should be done anyway to correctly support logging from BitBake), so this has also been fixed. [RP: Sync with logging changes] (Bitbake rev: 79751524cb1f0388975c6228f8c112e6af80f154) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake-layers: show help with no command specified

2011-08-15T08:49:11+00:00

Instead of running show_appends when no command is specified, show the default help text. Running show_appends by default made sense previously when that was the only real command provided, but now we have several useful commands implemented. (Bitbake rev: 62a2e0aa1ac8a459928d1f72783b6ca9c1756350) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake-layers: improve default command help

2011-08-15T08:49:11+00:00

Improve default help output and make unrecognised commands print it out rather than just an error. (Bitbake rev: 84f20eb874e7e0ae59bc76883ba9698b0cfcdb6b) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake/logging: Overhaul internal logging process

2011-08-15T08:14:28+00:00

At the moment it bugs me a lot that we only have one effective logging level for bitbake, despite the logging module having provision to do more advanced things. This patch: * Changes the core log level to the lowest level we have messages of (DEBUG-2) so messages always flow through the core logger * Allows build.py's task logging code to log all the output regardless of what output is on the console and sets this so log files now always contain debug level messages even if these don't appear on the console * Moves the verbose/debug/debug-domains code to be a UI side setting * Adds a filter to the UI to only print the user requested output. The result is more complete logfiles on disk but the usual output to the console. There are some behaviour changes intentionally made by this patch: a) the -v option now controls whether output is tee'd to the console. Ultimately, we likely want to output a message to the user about where the log file is and avoid placing output directly onto the console for every executing task. b) The functions get_debug_levels, the debug_levels variable, the set_debug_levels, the set_verbosity and set_debug_domains functions are removed from bb.msg. c) The "logging" init function changes format. d) All messages get fired to all handlers all the time leading to an increase in inter-process traffic. This could likely be hacked around short term with a function for a UI to only request events greater than level X. Longer term, having masks for event handlers would be better. e) logger.getEffectiveLevel() is no longer a reliable guide to what will/won't get logged so for now we look at the default log levels instead. [YOCTO #304] (Bitbake rev: 45aad2f9647df14bcfa5e755b57e1ddab377939a) Signed-off-by: Richard Purdie

bitbake-layers: adapt to cooker change for saved environment

2011-07-26T12:46:32+00:00

The Cooker requires a copy of the environment mapping, modify bitbake-layers to take one and pass it to the cooker. (Bitbake rev: f5653e557b68a27e99a2a6a5c5a31d0ba0b56bcb) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

Update version to 1.13.3

2011-07-25T13:36:00+00:00

(Bitbake rev: f0b5d16426b983a67c51c47f3542162108bd4156) Signed-off-by: Richard Purdie

bitbake|cooker: save a copy of the environment when BitBake is started

2011-07-25T11:54:17+00:00

Create a data store in the cooker containing the values of the environment from when BitBake is launched such that child processes can replicate (and/or use values from) the host environment, rather than the cleaned up environment that the main BitBake process uses. (Bitbake rev: 54c7206165c0e7cfe5f7b243c80461baf5e7dfb1) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

bitbake-layers: remove unneeded do_EOF

2011-07-25T11:54:17+00:00

do_EOF is only needed when using the Python cmd class in line-oriented mode - we are just sending single commands to it. (Bitbake rev: 0cbf5dcaf9f67522bd58d868aa01f28e846dfc19) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie