i'm reading this out of the current bitbake manual and it *seems* pretty straightforward but i'm always paranoid. here's the passage:
"BitBake will first search the current working directory for an optional "conf/bblayers.conf" configuration file. This file is expected to contain a BBLAYERS variable which is a space delimited list of 'layer' directories. For each directory in this list, a "conf/layer.conf" file will be searched for and parsed with the LAYERDIR variable being set to the directory where the layer was found. The idea is these files will setup BBPATH and other variables correctly for a given build directory automatically for the user. "BitBake will then expect to find 'conf/bitbake.conf' somewhere in the user specified BBPATH. That configuration file generally has include directives to pull in any other metadata (generally files specific to architecture, machine, local and so on)." fair enough. so if i'm using only oe-core, then i can use $ bitbake-layers show-layers to see that i'm using just that one layer: meta /home/rpjday/oe/oe-core/meta 5 which means that i will parse the file meta/conf/bitbake.conf, which eventually parses all of this: include conf/site.conf include conf/auto.conf include conf/local.conf include conf/build/${BUILD_SYS}.conf include conf/target/${TARGET_SYS}.conf include conf/machine/${MACHINE}.conf include conf/machine-sdk/${SDKMACHINE}.conf include conf/distro/${DISTRO}.conf include conf/distro/defaultsetup.conf include conf/documentation.conf require conf/sanity.conf require conf/abi_version.conf so here's the question(s). first, i'm assuming those conf files are processed in exactly that order, right? and second, all of that parsing and including is done and completed before reading the first line of the task or recipe file that's the bitbake target, right? as i said, i'm pretty sure that's correct but i want to make absolutely sure before i ask followup questions. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core