7837 2015-06-01 21:56:46 +0000 site.conf not acting as implied by docs. 2016-05-19 14:41:51 +0000 1 1 7 Build System, Metadata & Runtime OE-Core configuration unspecified All Multiple RESOLVED FIXED Low normal 2.2 1 brian.avery richard.purdie bluelightning liezhi.yang ross.burton alexandru.c.georgescu --- --- Don't know oldest_to_newest 51403 0 brian.avery 2015-06-01 21:56:46 +0000 In section 3.1, the docs imply that I can make a site.conf file to configure multiple builds simultaneously. It also indicates that I can "extend your BBPATH variable to include the path to a conf/site.conf. Then, when BitBake looks for Metadata using BBPATH, it finds the conf/site.conf file and applies your common configurations found in the file." But, the default bblayers.conf does a BBPATH = "${TOPDIR}" which means that any BBPATH env settings I have are wiped out. Having to append the bbpath in each bblayers.conf file seems to somewhat obviate the advantages of a site.conf file. For my curent usage model, changing the default bblayers.conf to do BBPATH .= ":${TOPDIR}" works, but it breaks sanity check if you don't have BBPATH in your env since you end up with an empty :: which is the same as having a "." in BBPATH. Initial ideas on how to address: 1) use BBPATH .= ":${TOPDIR}" in bblayers.conf and then strip out any :: in bbpath. 2) add an additional var BBPATH_SITE to list sitewide places to search 61215 1 richard.purdie 2016-04-14 14:40:40 +0000 *** Bug 9422 has been marked as a duplicate of this bug. *** 62321 2 ross.burton 2016-05-19 14:41:51 +0000 Fixed in oe-core a3d223284854a21c84e8f6d075d23b32789afa01