Skip to contentSkip to conversation

layer.conf/bblayers.conf.sample: Fix empth BBPATH entry warnings

PATCH In review Richard Purdie 2 participants 2 messages Jun 22, 2012

lore
Share & tools
lore

Richard Purdie

author
#0 lore raw

PATCH 1/1 layer.conf/bblayers.conf.sample: Fix empth 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.

Signed-off-by Richard Purdie <[email protected]>
---
 meta/conf/bblayers.conf.sample |    4 +++-
 meta/conf/layer.conf           |    1 -
 2 files changed, 3 insertions(+), 2 deletions(-)
meta/conf/bblayers.conf.sample +3 -1
index 222b03a..e621866 100644
@@ -1,8 +1,10 @@
 # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
 # changes incompatibly
-LCONF_VERSION = "4"
+LCONF_VERSION = "5"
 
+BBPATH = "${TOPDIR}"
 BBFILES ?= ""
+
 BBLAYERS ?= " \
   ##COREBASE##/meta \
   "
meta/conf/layer.conf +0 -1
index 43e4295..090c8e2 100644
@@ -1,4 +1,3 @@
-BBPATH ?= ""
 # We have a conf and classes directory, add to BBPATH
 BBPATH .= ":${LAYERDIR}"
 # We have a packages directory, add to BBFILES
#1 lore raw
Quoted 9 lines · Richard Purdie

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.

Quoted 5 lines

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.

thanks this is fine

Quoted 39 lines
Signed-off-by Richard Purdie <[email protected]>

---
 meta/conf/bblayers.conf.sample |    4 +++-
 meta/conf/layer.conf           |    1 -

 2 files changed, 3 insertions(+), 2 deletions(-)
meta/conf/bblayers.conf.sample +2 -1
index 222b03a..e621866 100644
@@ -1,8 +1,10 @@
  # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
  # changes incompatibly
-LCONF_VERSION = "4"
+LCONF_VERSION = "5"
 
+BBPATH = "${TOPDIR}"

 BBFILES ?= ""
+
 BBLAYERS ?= " \
  ##COREBASE##/meta \
  "

meta/conf/layer.conf +0 -1
index 43e4295..090c8e2 100644
@@ -1,4 +1,3 @@
-BBPATH ?= ""
  # We have a conf and classes directory, add to BBPATH

 BBPATH .= ":${LAYERDIR}"
 # We have a packages directory, add to BBFILES

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core