openembedded-core.git/oe-init-build-env-memres, branch master-next2

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

oe-init-build-env-memres: Fix source check

2015-03-20T10:55:18+00:00

The source check was referring to oe-init-build-env instead of the
memres. It could be executed without the proper failure message and the
corresponding exit command out of the script. This commit makes the
memres script look more like the oe-init-build-env with the correct
script name.

[YOCTO #7487]

Signed-off-by: Benjamin Esquivel 
Signed-off-by: Richard Purdie

oe-init-build-env-memres: Fix automatic port usage

2014-09-23T18:59:44+00:00

The use of an automatic port wasn't working correctly since the server
was never getting started when port == -1. This fixes things so the
server is started when port is not specified (i.e. automatic) ensuring
this happens before BBSERVER is set.

[YOCTO #6563]

Signed-off-by: Richard Purdie

oe-init-build-env-memres: Add auto port functionality

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

In order to run multiple bitbake memory resident servers on the same
machine they must each use different ports.

This patch works in conjuction with bitbake to make the auto port
selection and lazy server startup the default.

Signed-off-by: Jason Wessel 
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

oe-init-build-env-memres: Unset BBSERVER if already set

2013-10-04T17:25:38+00:00

When starting a new server we don't want bitbake to connect to an existing
server so ensure BBSERVER is unset.

Signed-off-by: Richard Purdie

oe-init-build-env-memres: use shell instead of Python to show the port number

2013-09-26T16:08:09+00:00

Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie