linux/poky.git/oe-init-build-env, branch yocto-2.1.1

oe-init-build-env*: Make them actually return failures

2016-03-20T23:12:30+00:00

If either of the internal scripts (oe-buildenv-internal and oe-setup-builddir) failed, oe-init-build-env (and oe-init-build-env-memres) would still return success. (From OE-Core rev: 40764c7039f1ee161916d4fbf7dfe15fb964030e) Signed-off-by: Peter Kjellerstedt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe-init-build-env*: Remove unnecessary differences between the scripts

2016-03-20T23:12:30+00:00

While at it, also fix: * consistent indentation (four spaces) * unset temporary variables * use $(...) instead of `...` (From OE-Core rev: 1295d413f27941d0763a3d58982378738bf3ca06) Signed-off-by: Peter Kjellerstedt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe-init-build-env*: Update/correct comment about specifying arguments

2016-03-20T23:12:30+00:00

(From OE-Core rev: 9c7e3cfcff08bd47b0c1eeb63d8055d8a8b12935) Signed-off-by: Peter Kjellerstedt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe-init-build-env*: Allow $OEROOT to be predefined

2016-03-20T23:12:30+00:00

The current implementation of oe-init-build-env and oe-init-build-env-memres requires that they are sourced from the directory that will be known as $OEROOT. This makes it hard to write a wrapper script with the same name as the original OE script which, e.g., sources the original OE script from a sub-directory. With this change, $OEROOT can be predefined when oe-init-build-env or oe-init-build-env-memres is sourced, allowing the original OE scripts to be anywhere. (From OE-Core rev: 3327e2a9222004d8ac7974cb1d9fe77c81176cfc) Signed-off-by: Peter Kjellerstedt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

scripts: hand the TEMPLATECONF local over to setup-builddir

2015-12-28T09:25:19+00:00

(From OE-Core rev: 0bf9d919bba5780d34cc6ac9dde2c74bb07b8342) Signed-off-by: Marcus Müller Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe-init-build-env: fix for build dirs that have spaces in their path

2015-04-13T21:33:24+00:00

Enclose expansions of BUILDDIR in quotes in order to correctly handle paths which include spaces. (From OE-Core rev: 0c08723cf5ebc1a7df7dc4ca36cffa090286468c) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

oe-init-build-env: Improve script sourcing detection.

2014-03-11T15:11:41+00:00

This script is only useful when sourced into a shell. These changes improve the detection of this operation, no matter how the script is referenced. (From OE-Core rev: cac863e958a0c8fe0f8a84dc194273c699f0c40f) Signed-off-by: Gary Thomas Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

oe-init-build-env: Allow startup with and without memres

2013-12-02T11:28:27+00:00

Use the bitbake --status-only and the fact that bitbake.lock will contain the host name and port to determine when to activate or shutdown the stay resident bitbake server. This allows a end developer to cleanly switch between the two ways to use bitbake as well as enter the memres bitbake server from multiple shells without starting the server if it is already running. (From OE-Core rev: d71059c86a8160f39af6ddfdd30c86835f4eb959) Signed-off-by: Jason Wessel Signed-off-by: Richard Purdie

oe-init-build-env: unset BBSERVER

2013-10-07T08:37:31+00:00

If BBSERVER is set, we should unset it before proceeding. Its assumed the user will have unloaded the server from memory should they have wished to do so. (From OE-Core rev: 5cc4d315709de195bfb0655c2f00ae2267bfa4c6) Signed-off-by: Richard Purdie

oe-init-build-env: Make it use the correct $OEROOT with zsh

2013-04-05T22:05:34+00:00

(From OE-Core rev: f0aa69296f4c1d4214f9dbea236b0ed330b8154b) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie