summaryrefslogtreecommitdiff
path: root/poky-init-build-env
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2011-02-23 13:13:31 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-02-23 13:13:31 +0000
commit101b599110f7bc29f52a14a968f30323aeb797ca (patch)
tree2ed171b52eab7961215f105eb9982b7fa128ae68 /poky-init-build-env
parent6ea24f04cd635295d826f03d9c7d8a08cc1d5b31 (diff)
downloadopenembedded-core-101b599110f7bc29f52a14a968f30323aeb797ca.tar.gz
openembedded-core-101b599110f7bc29f52a14a968f30323aeb797ca.tar.bz2
openembedded-core-101b599110f7bc29f52a14a968f30323aeb797ca.tar.xz
openembedded-core-101b599110f7bc29f52a14a968f30323aeb797ca.zip
bitbake/data_smart: Improve Variable expansion error handling
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 <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'poky-init-build-env')
0 files changed, 0 insertions, 0 deletions