bitbake: Sync with upstream
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5350 311d38ba-8fff-0310-9ca6-ca027cbcb966
This commit is contained in:
parent
419f18450d
commit
efe3d75208
|
@ -149,6 +149,11 @@ Changes in Bitbake 1.9.x:
|
||||||
- Fix PACKAGES_DYNAMIC handling of packages with '++' in the name
|
- Fix PACKAGES_DYNAMIC handling of packages with '++' in the name
|
||||||
- Rename __depends to __base_depends after configuration parsing so we don't
|
- Rename __depends to __base_depends after configuration parsing so we don't
|
||||||
recheck the validity of the config files time after time
|
recheck the validity of the config files time after time
|
||||||
|
- Add better environmental variable handling. By default it will now only pass certain
|
||||||
|
whitelisted variables into the data store. If BB_PRESERVE_ENV is set bitbake will use
|
||||||
|
all variable from the environment. If BB_ENV_WHITELIST is set, that whitelist will be
|
||||||
|
used instead of the internal bitbake one. Alternatively, BB_ENV_EXTRAWHITE can be used
|
||||||
|
to extend the internal whitelist.
|
||||||
|
|
||||||
Changes in Bitbake 1.8.0:
|
Changes in Bitbake 1.8.0:
|
||||||
- Release 1.7.x as a stable series
|
- Release 1.7.x as a stable series
|
||||||
|
|
|
@ -54,6 +54,11 @@ Changes in BitBake 1.8.x:
|
||||||
- Fix PACKAGES_DYNAMIC handling of packages with '++' in the name
|
- Fix PACKAGES_DYNAMIC handling of packages with '++' in the name
|
||||||
- Rename __depends to __base_depends after configuration parsing so we don't
|
- Rename __depends to __base_depends after configuration parsing so we don't
|
||||||
recheck the validity of the config files time after time
|
recheck the validity of the config files time after time
|
||||||
|
- Add better environmental variable handling. By default it will now only pass certain
|
||||||
|
whitelisted variables into the data store. If BB_PRESERVE_ENV is set bitbake will use
|
||||||
|
all variable from the environment. If BB_ENV_WHITELIST is set, that whitelist will be
|
||||||
|
used instead of the internal bitbake one. Alternatively, BB_ENV_EXTRAWHITE can be used
|
||||||
|
to extend the internal whitelist.
|
||||||
|
|
||||||
Changes in BitBake 1.8.10:
|
Changes in BitBake 1.8.10:
|
||||||
- Psyco is available only for x86 - do not use it on other architectures.
|
- Psyco is available only for x86 - do not use it on other architectures.
|
||||||
|
|
|
@ -176,7 +176,7 @@ def better_exec(code, context, text, realfile):
|
||||||
raise
|
raise
|
||||||
|
|
||||||
# print the Header of the Error Message
|
# print the Header of the Error Message
|
||||||
bb.msg.error(bb.msg.domain.Util, "Error in executing: ", realfile)
|
bb.msg.error(bb.msg.domain.Util, "Error in executing: %s" % realfile)
|
||||||
bb.msg.error(bb.msg.domain.Util, "Exception:%s Message:%s" % (t,value) )
|
bb.msg.error(bb.msg.domain.Util, "Exception:%s Message:%s" % (t,value) )
|
||||||
|
|
||||||
# let us find the line number now
|
# let us find the line number now
|
||||||
|
|
Loading…
Reference in New Issue