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

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

2017-07-21T07:44:25+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. (From OE-Core rev: a17724d687f9c04dc21f2f369da2b492f7119ba0) Signed-off-by: Richard Purdie

oe-init-build-env-memres: swap parameter order

2017-06-28T14:52:17+00:00

This script expected the port number to be specified first, which is somewhat counter-intuitive especially if you're used to oe-init-build-env; besides, in local usage you are unlikely to need to specify a custom port. Given that few people are using this yet (based on the issues I have recently fixed), switch the arguments around so that the two scripts behave consistently. (From OE-Core rev: 5d8f4c46329fbd38ebd034c1e32aa49dfec5f529) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

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

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

2015-03-20T10:56:03+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] (From OE-Core rev: 1666b41e73f2aa7bd736c3e9bf3797946bff61b5) Signed-off-by: Benjamin Esquivel Signed-off-by: Richard Purdie

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

2014-09-23T19:06:06+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] (From OE-Core rev: 982553b6d56ca4bfd095c1bcb736ae3b77deefa7) Signed-off-by: Richard Purdie

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

2013-12-02T11:28:27+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. (From OE-Core rev: 9cf1ac73c4e35101a4f5c01a5e1c53f9d567bc58) Signed-off-by: Jason Wessel 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