openembedded-core.git/oe-init-build-env, branch thud

oe-init-build-env: Error out when failed to locate cwd

2019-04-13T19:32:44+00:00

Ubuntu's /bin/sh symlinks to /bin/dash by default, so
subprocess.check_call(oe-init-build-env, cwd=builddir) would be failed since
pwd is builddir, and there is no $builddir/oe-init-build-env, this would
lead to other confusing errors, check and error it out earlier to make it
easier to locate the problem.

We don't meet the problem when manually run ". oe-init-build-env" is because
Ubuntu's default login shell is bash, but subprocess.check_call() doesn't
respect to login shell, so the error only happens in situations like
subprocess.check_call().

And also print errors to stderr as oe-buildenv-internal does.

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie 
Signed-off-by: Armin Kuster

oe-init-build-env-memres: Drop it

2017-07-21T07:44:18+00:00

With the new server structure we no longer need this separate
environment init script. Just set BB_SERVER_TIMEOUT to be greater
than zero and bitbake will remain in memory and the UI will auto-reconnect
to it.

Also clean out the old shutdown code from oe-init-build-env which
also doesn't make sense now.

Signed-off-by: Richard Purdie

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

2016-03-20T22:57:59+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.

Signed-off-by: Peter Kjellerstedt 
Signed-off-by: Ross Burton

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

2016-03-20T22:57:58+00:00

While at it, also fix:
* consistent indentation (four spaces)
* unset temporary variables
* use $(...) instead of `...`

Signed-off-by: Peter Kjellerstedt 
Signed-off-by: Ross Burton

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

2016-03-20T22:57:58+00:00

Signed-off-by: Peter Kjellerstedt 
Signed-off-by: Ross Burton

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

2016-03-20T22:57:58+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.

Signed-off-by: Peter Kjellerstedt 
Signed-off-by: Ross Burton

scripts: hand the TEMPLATECONF local over to setup-builddir

2015-12-27T11:27:01+00:00

Signed-off-by: Marcus Müller 
Signed-off-by: Ross Burton

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

2015-04-13T21:29:04+00:00

Enclose expansions of BUILDDIR in quotes in order to correctly handle paths
which include spaces.

Signed-off-by: Joshua Lock 
Signed-off-by: Richard Purdie

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

2014-03-11T15:09:04+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.

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:27:36+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.

Signed-off-by: Jason Wessel 
Signed-off-by: Richard Purdie