summaryrefslogtreecommitdiffstats
path: root/poky-init-build-env
diff options
context:
space:
mode:
authorJoshua Lock <josh@linux.intel.com>2010-07-21 14:55:39 +0100
committerRichard Purdie <rpurdie@linux.intel.com>2010-07-21 15:39:53 +0100
commit971907567cff64e74f21d349d6751dadc8c09827 (patch)
treee0cfd7ee0ba3091272eca5c5f1b90edffc3653aa /poky-init-build-env
parent50629b3746c149b22bdd8664842a4c69abb2b989 (diff)
downloadpoky-971907567cff64e74f21d349d6751dadc8c09827.tar.gz
Enable build dir outside of the poky directory
You need to first set up the build directory by sourcing the poky build script, after that builds can be run in that directory so long as bitbake is in $PATH removing the need to source the init script for each build. i.e: $ . poky-init-build-env ~/my-build $ bitbake some-image <<later, in a different shell>> $ cd ~/my-build $ export PATH=/path/to/bitbake/bin:$PATH $ bitbake an-image This patch also removes use of OEROOT in recipes, etc. Signed-off-by: Joshua Lock <josh@linux.intel.com>
Diffstat (limited to 'poky-init-build-env')
-rwxr-xr-xpoky-init-build-env4
1 files changed, 3 insertions, 1 deletions
diff --git a/poky-init-build-env b/poky-init-build-env
index 94bf3f0f7f..0f5e684a52 100755
--- a/poky-init-build-env
+++ b/poky-init-build-env
@@ -21,7 +21,9 @@
21 21
22if test x"$0" = x"./poky-init-build-env"; then 22if test x"$0" = x"./poky-init-build-env"; then
23 echo "Error: Run via '. ./poky-init-build-env'" 23 echo "Error: Run via '. ./poky-init-build-env'"
24elif test x"$BASH_SOURCE" = x; then
25 echo "Error: you are not running a Bash shell, please use Bash or add support for your shell to the init scripts"
24else 26else
25 . ./scripts/poky-env-internal 27 . `dirname $BASH_SOURCE`/scripts/poky-env-internal
26fi 28fi
27 29