Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH] Allow environment variables and ~ in bbconf paths
Date: Tue, 14 Apr 2015 23:45:50 +0300	[thread overview]
Message-ID: <1429044350-19766-1-git-send-email-ed.bartosh@linux.intel.com> (raw)

This should allow to use ~, $HOME and other environment
variables in bbconf paths.

Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
---
 bitbake/lib/bb/cookerdata.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bitbake/lib/bb/cookerdata.py b/bitbake/lib/bb/cookerdata.py
index 6c11a60..ec5c9ea 100644
--- a/bitbake/lib/bb/cookerdata.py
+++ b/bitbake/lib/bb/cookerdata.py
@@ -271,6 +271,7 @@ class CookerDataBuilder(object):
             data = bb.data.createCopy(data)
             for layer in layers:
                 parselog.debug(2, "Adding layer %s", layer)
+                layer = os.path.expanduser(os.path.expandvars(layer))
                 data.setVar('LAYERDIR', layer)
                 data = parse_config_file(os.path.join(layer, "conf", "layer.conf"), data)
                 data.expandVarref('LAYERDIR')
-- 
2.1.4



             reply	other threads:[~2015-04-14 20:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 20:45 Ed Bartosh [this message]
2015-04-14 21:19 ` [PATCH] Allow environment variables and ~ in bbconf paths Rifenbark, Scott M
2015-04-14 21:33   ` Christopher Larson
2015-04-15 11:48     ` Ed Bartosh
2015-04-15 14:43     ` [PATCH] bitbake: Allow environment variables and ~ in bblayers Ed Bartosh
2015-04-15 19:38       ` Christopher Larson
2015-04-16 18:28         ` [PATCH] bitbake: Allow " Ed Bartosh
2015-04-17 10:41           ` Richard Purdie
2015-04-17 11:18             ` Gary Thomas
2015-04-18 15:09             ` Ed Bartosh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1429044350-19766-1-git-send-email-ed.bartosh@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox