summaryrefslogtreecommitdiffstats
path: root/meta-crownbay
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:15:37 -0500
commit19740c20016561d691bf1f45e213c45213faafd2 (patch)
treebcb0ee105b7cf102edab28d7b47cb5e65be2fb08 /meta-crownbay
parent2e1cc12ddb955fa558f42e1845d42e7f65a5156a (diff)
downloadmeta-intel-19740c20016561d691bf1f45e213c45213faafd2.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-crownbay')
0 files changed, 0 insertions, 0 deletions