summaryrefslogtreecommitdiff
path: root/oe-init-build-env
AgeCommit message (Collapse)AuthorFiles
2016-03-20oe-init-build-env*: Make them actually return failuresPeter Kjellerstedt1
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>
2016-03-20oe-init-build-env*: Remove unnecessary differences between the scriptsPeter Kjellerstedt1
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>
2016-03-20oe-init-build-env*: Update/correct comment about specifying argumentsPeter Kjellerstedt1
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-03-20oe-init-build-env*: Allow $OEROOT to be predefinedPeter Kjellerstedt1
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>
2015-12-27scripts: hand the TEMPLATECONF local over to setup-builddirMarcus Müller1
Signed-off-by: Marcus Müller <marcus.mueller@ettus.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-04-13oe-init-build-env: fix for build dirs that have spaces in their pathJoshua Lock1
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>
2014-03-11oe-init-build-env: Improve script sourcing detection.Gary Thomas1
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>
2013-12-02oe-init-build-env: Allow startup with and without memresJason Wessel1
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>
2013-10-04oe-init-build-env: unset BBSERVERRichard Purdie1
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>
2013-04-05oe-init-build-env: Make it use the correct $OEROOT with zshPeter Kjellerstedt1
Signed-off-by: Peter Kjellerstedt <pkj@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-26Various typoes fixed, all comments or output strings.Robert P. J. Day1
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>
2011-08-02oe-init-build-env, scripts/oe-buildenv-internal: add error detecting for $BDIRDexuan Cui1
[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>
2011-04-21Further cleanup of various poky referencesRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20poky-setup-builddir: Rename to oe-setup-builddir and clean up POKY variable ↵Richard Purdie1
references Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20oe-init-build-env: Fix typoRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-04-20Rename poky-init-build-env to oe-init-build-envRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 23:23:53 +0000