summaryrefslogtreecommitdiffstats
path: root/meta-tlk/conf
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-23 13:26:47 +0100
committerTom Zanussi <tom.zanussi@linux.intel.com>2013-04-23 08:18:25 -0500
commitbead07dfcad26fa616190d31b32bb2d712bbe025 (patch)
treebcb0ee105b7cf102edab28d7b47cb5e65be2fb08 /meta-tlk/conf
parentdaeab7fe6781dc3ddeb0adb98175ad767cde1b7d (diff)
downloadmeta-intel-bead07dfcad26fa616190d31b32bb2d712bbe025.tar.gz
meta-jasperforest: Fix BBFILES
BBFILES is whitespace delimited. If .= used, no whitespace padding is added around the addition and this can lead to it being combined with some other part of the field, leading to parts of BBFILES mysteriously not being seen. For example, I have in my bblayers.conf: /media/build1/poky/meta-intel/meta-emenlow \ /media/build1/poky/meta-intel/meta-fri2 \ /media/build1/poky/meta-intel/meta-jasperforest \ /media/build1/poky/meta-intel/meta-n450 \ /media/build1/poky/meta-intel/meta-romley \ and this results in the warning: WARNING: No bb files matched BBFILE_PATTERN_fri2 '^/media/build1/poky/meta-intel/meta-fri2/' and if I try to build MACHINE=fri2, I get strange errors due to the .bb files not being parsed. The fix is simply to use +=, just like every other layer.conf file. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Diffstat (limited to 'meta-tlk/conf')
0 files changed, 0 insertions, 0 deletions