linux/poky.git/bitbake/lib/bb/parse/parse_py/ConfHandler.py, branch bernard

parse: pass filename, lineno into the ast

2011-01-10T13:24:03+00:00

We will be needing this information to improve the tracebacks of python code from the metadata, as well as to give the user information about where variables were defined, so they know how it ended up the way it is. (Bitbake rev: 9615c538b894f71a2d1a0ba6b3f260db91e75786) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

ConfHandler: commentary typo fixes

2011-01-04T15:00:25+00:00

(Bitbake rev: 089dc31932a85455ed0fec8209d0451af4310f94) Signed-off-by: Bernhard Reutner-Fischer Signed-off-by: Richard Purdie

Switch bitbake internals to use logging directly rather than bb.msg

2011-01-04T14:46:33+00:00

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 Signed-off-by: Richard Purdie

Move the unset BBPATH sanity check after the bblayers processing

2010-07-02T14:41:33+00:00

This way we can fully utilize bblayers, you can do everything in bblayers.conf and avoid setting any environment variables at all. (Bitbake rev: 5def1c8c31432968349f9b29d6333d7962260a8b) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Apply some 2to3 transforms that don't cause issues in 2.6

2010-07-02T14:41:33+00:00

(Bitbake rev: d39ab776e7ceaefc8361150151cf0892dcb70d9c) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Import fixups

2010-07-02T14:41:32+00:00

(Bitbake rev: 4fa052f426e3205ebace713eaa22deddc0420e8a) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Formatting cleanups

2010-07-02T14:41:32+00:00

(Bitbake rev: 2caf134b43a44dad30af4fbe33033b3c58deee57) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Stop using functions via 'bb' that were moved from there to other modules

2010-07-02T14:41:32+00:00

(Bitbake rev: 03a6c26f8da226f442c3cab557e4733f7cd6eeac) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Ensure we always utilize the correct messaging domains

2010-07-02T14:41:31+00:00

(Bitbake rev: 92a2e2e90981c0615171abe03645a772d84f6986) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Implement ??= operator

2010-03-22T15:02:59+00:00

??= is a lazy, conditional assignment. Whereas a ?= immediately assigns to the variable if the variable has not yet been set, ??= does not apply the default assignment until the end of the parse. As a result, the final ??= for a given variable is used, as opposed to the first as in ?=. Note that the initial implementation relies upon finalise() to apply the defaults, so a "bitbake -e" without specifying a recipe will not show the defaults as set by ??=. Moving application of the default into getVar adds too large a performance hit. We may want to revisit this later. (Bitbake rev: 74f50fbca194c9c72bd2a540f4b9de458cb08e2d) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie