linux/poky.git/bitbake/lib/bb/parse/parse_py/ConfHandler.py, branch laverne-4.0

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

Error early if BBPATH is unset, rather than falling back to share/bitbake

2010-03-22T14:56:00+00:00

Better to error as early as possible rather than experience strange behavior resulting from the use of the largely useless stock bitbake.conf/base.bbclass. (Bitbake rev: 641e6cf3ec3ab4d26929cf4d2a3704ff07eed4d6) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

bitbake: [parser] Make resolve_file only resolve the path

2010-02-15T17:07:55+00:00

Do not attempt to open the file in the resolve_file method (a lot like bb.which... maybe bb.which can be used). This way we don't need to open/close a file which we have already parsed. Signed-off-by: Richard Purdie

bitbake: [parser] Remove the "data" from feeder, evaluate after parsing a file

2010-02-15T17:07:51+00:00

Evaluate the statements after having parsed one file. This is referred to as "entwirren" and we can remove the direct evaluation and postpone a bit, in the future we can use a cached copy instead of parsing the original. Signed-off-by: Richard Purdie