summaryrefslogtreecommitdiffstats
path: root/meta-yocto/conf/local.conf.sample
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2012-06-22 14:33:12 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-06-25 16:35:55 +0100
commit5e3a61b40b7b697d83b41e7e247cd1f94eb7673c (patch)
tree7457543434b68420f33b4e585b9dfcfe6a8fed2b /meta-yocto/conf/local.conf.sample
parent4d7636322c8b5bfbbdd82a5b434a79b0e49f62cc (diff)
downloadpoky-5e3a61b40b7b697d83b41e7e247cd1f94eb7673c.tar.gz
bblayers.conf.sample: Fix empty BBPATH entry warnings
Many people are seeing issues from the empty path warnings from BBPATH. The empty path entry corresponding to the current working directory is a problem since if cwd changes, so does BBPATH and build reproducibility. Simply removing the empty element causes problems since the build directory then isn't listed in BBPATH which means local.conf isn't found and this gives an extremely confusing error message about bbappends being unsatisfied. The build directory in bitbake terms is TOPDIR. The correct way to fix things is to add in TOPDIR into bblayers.conf itself. This means the layers can happily append/prepend to BBPATH at will as its no longer empty hence neatly solving all the various problems. Since the file has changed, the version is also changed. (From meta-yocto rev: 7bbbedf64b0820cacffe723789486d3081894827) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto/conf/local.conf.sample')
0 files changed, 0 insertions, 0 deletions