openembedded-core.git/bitbake/lib/bb/data_smart.py, branch pyro

bitbake: Remove in-tree version

2011-02-23T18:48:51+00:00

Bitbake should be used by checking it out from its own repo

Signed-off-by: Khem Raj

bitbake/data_smart: Improve Variable expansion error handling

2011-02-23T13:13:31+00:00

If expanding a variable triggers an exception the caller currently has no
way to supress the error message or otherwise handle the siutation. An
example of where this is a problem is "bitbake -e" showing tracebacks and
errors for variables like SRCPV in OE/Poky.

Secondly in a chained expansion fails, log mesages are recorded for
every step of the expansion, not just the innermost error which is
where the real failure occured.

To fix this we introduce a new exception ExpansionError which callers
can handle as appropriate.

Signed-off-by: Richard Purdie

bitbake/data_smart: Improve the way lazyassignment works

2011-02-23T11:48:01+00:00

Currently, if a variable has been set with ??= and the code looks it up
before the data finalisation phase, no value is found. This is causes
serious problems for anonymous python functions which manipulate data, or
for the fetcher revision handling code where revisions can be set with
??=.

There is also a significant performance implication for processing lazy
assignment in finalise.

Moving the check for a default value into getVarFlag addresses both
the timing issue and the performace. This change gives a 7% real time
performance improvement to parsing the Poky metadata. The cost of the
check at this point is minimal since we have all the data flags available.

This should also fix Yocto bug 752.

Signed-off-by: Richard Purdie

bitbake: Sync a load of whitespace and other non-functionality changes with bitbake uptream

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

Signed-off-by: Richard Purdie

Move LAYERDIR expansion hack into DataSmart

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

(Bitbake rev: 40778a6e9e82c7ea4673a74fc19574430fa63e8d)

Signed-off-by: Chris Larson 
Signed-off-by: Richard Purdie

build: use bb.process instead of os.system

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

(Bitbake rev: 53740977521bc81ffa37adfa7bbeb8f2a80ea165)

build: write logfiles per task, not per function
Based on d14f9bf6 from poky, reworked for master and other cleanup.

(Bitbake rev: beadff2eca1eb95f0411115dd72ddb4c3c44c604)

Signed-off-by: Chris Larson 
Signed-off-by: Richard Purdie

Access metadata vars as locals in python snippets

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

Example:
FOO = "bar"
BAR = "${@FOO + '/baz'}"

${BAR} == "bar/baz"

(Bitbake rev: 606fa1fd97cbd47a6a7ebdc7a2e6aa93a8f65cf5)

Signed-off-by: Chris Larson 
Signed-off-by: Richard Purdie

Fix getitem for DataSmart

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

Ensure it raises KeyError for a missing key, this is required to use this as a
mapping in various places, e.g. as locals in an eval.

(Bitbake rev: 8d661ce0c303e8d69f17c1d095545d5ed086d1d5)

Signed-off-by: Chris Larson 
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

Make DataSmart inherit the MutableMapping ABC

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

Provide __len__, __iter__, and the getitem/setitem/delitem methods, and its
mixed in versions of keys(), values(), items(), etc will automatically behave,
making the DataSmart act more like a real mapping.

(Bitbake rev: 89b5351c656d263b0ce513cee043bc046d20a01e)

Signed-off-by: Chris Larson 
Signed-off-by: Richard Purdie