path: root/oe-init-build-env
Commit message (Collapse)AuthorAgeFilesLines
* meta/lib+scripts: Convert to SPDX license headersRichard Purdie2019-05-091-12/+1
| | | | | | | | | | | | | | | | | | | | | This adds SPDX license headers in place of the wide assortment of things currently in our script headers. We default to GPL-2.0-only except for the oeqa code where it was clearly submitted and marked as MIT on the most part or some scripts which had the "or later" GPL versioning. The patch also drops other obsolete bits of file headers where they were encoountered such as editor modelines, obsolete maintainer information or the phrase "All rights reserved" which is now obsolete and not required in copyright headers (in this case its actually confusing for licensing as all rights were not reserved). More work is needed for OE-Core but this takes care of the bulk of the scripts and meta/lib directories. The top level LICENSE files are tweaked to match the new structure and the SPDX naming. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env: Error out when failed to locate cwdRobert Yang2019-03-121-1/+6
| | | | | | | | | | | | | | | | | | 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 <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env-memres: Drop itRichard Purdie2017-07-211-8/+0
| | | | | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* oe-init-build-env*: Make them actually return failuresPeter Kjellerstedt2016-03-201-3/+7
| | | | | | | | | 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 <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
* oe-init-build-env*: Remove unnecessary differences between the scriptsPeter Kjellerstedt2016-03-201-11/+10
| | | | | | | | | | While at it, also fix: * consistent indentation (four spaces) * unset temporary variables * use $(...) instead of `...` Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
* oe-init-build-env*: Update/correct comment about specifying argumentsPeter Kjellerstedt2016-03-201-4/+4
| | | | | Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
* oe-init-build-env*: Allow $OEROOT to be predefinedPeter Kjellerstedt2016-03-201-7/+9
| | | | | | | | | | | | | | | 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 <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
* scripts: hand the TEMPLATECONF local over to setup-builddirMarcus Müller2015-12-271-1/+1
| | | | | Signed-off-by: Marcus Müller <marcus.mueller@ettus.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
* oe-init-build-env: fix for build dirs that have spaces in their pathJoshua Lock2015-04-131-1/+1
| | | | | | | | Enclose expansions of BUILDDIR in quotes in order to correctly handle paths which include spaces. Signed-off-by: Joshua Lock <joshua.lock@collabora.co.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env: Improve script sourcing detection.Gary Thomas2014-03-111-19/+23
| | | | | | | | | | 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 <gary@mlbassoc.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env: Allow startup with and without memresJason Wessel2013-12-021-0/+9
| | | | | | | | | | | | | 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 <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env: unset BBSERVERRichard Purdie2013-10-041-1/+4
| | | | | | | | 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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env: Make it use the correct $OEROOT with zshPeter Kjellerstedt2013-04-051-0/+2
| | | | | Signed-off-by: Peter Kjellerstedt <pkj@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Various typoes fixed, all comments or output strings.Robert P. J. Day2012-03-261-1/+1
| | | | | | | Typoes fixed: "enviroment", "editted", "spliting", "scheulder". Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env, scripts/oe-buildenv-internal: add error detecting for $BDIRDexuan Cui2011-08-021-3/+3
| | | | | | | | | | | | | | | | | | | | | | [YOCTO #671] "readlink -f" in Ubuntu 10.04 is buggy: it doesn't ignore a trailing / (e.g., "readlink -f /tmp/non-existent-dir/" returns nothing, but according to http://www.gnu.org/s/coreutils/manual/coreutils.pdf it should do that -- hence we get bug 671. It seems Ubuntu 10.10 or even later Ubuntu 11.04, and other Linux distributions(e.g., Open Suse 11.4) haven't such an issue. So I think we should detect this and ask Ubuntu 10.04 users to avoid supply a path with trailing slash here. Moreever, I also add the detection of non-existent path, e.g., source oe-init-build-env /non-existent-dir/build can be detected and we'll print an error msg. And, if we get errors in oe-buildenv-internal, we should stop the script and shouldn't further run. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Further cleanup of various poky referencesRichard Purdie2011-04-211-2/+2
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-setup-builddir: Rename to oe-setup-builddir and clean up POKY variable ↵Richard Purdie2011-04-201-1/+1
| | | | | | references Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env: Fix typoRichard Purdie2011-04-201-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename poky-init-build-env to oe-init-build-envRichard Purdie2011-04-201-0/+44
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>