summaryrefslogtreecommitdiff
path: root/handbook/ref-varlocality.xml
diff options
context:
space:
mode:
authorJeff Dike <jdike@linux.intel.com>2010-06-29 13:32:04 +0100
committerRichard Purdie <rpurdie@linux.intel.com>2010-06-29 13:32:04 +0100
commitf9d7e9e3be89ac9141fb0eb7c71eef5a9a82add9 (patch)
tree1ee1ed9eb7673f1556da0d52d14089a03d93f76f /handbook/ref-varlocality.xml
parent132122e31375117bf8b5ab68369cb8fafa03058d (diff)
downloadopenembedded-core-f9d7e9e3be89ac9141fb0eb7c71eef5a9a82add9.tar.gz
openembedded-core-f9d7e9e3be89ac9141fb0eb7c71eef5a9a82add9.tar.bz2
openembedded-core-f9d7e9e3be89ac9141fb0eb7c71eef5a9a82add9.tar.xz
openembedded-core-f9d7e9e3be89ac9141fb0eb7c71eef5a9a82add9.zip
bitbake: Move the logger initialization from cooker to utils
In order to move the environment cleaning, which wants to log a message, before cooker creation, the logging facility initialization needs to happen earlier. So, it is now in init_logger in utils.py and called from bitbake before the creation of the data object. It also seems more correct to initialize a global facility like this from a more global context than the creation of an object, of which there could theoretically be many. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'handbook/ref-varlocality.xml')
0 files changed, 0 insertions, 0 deletions