summaryrefslogtreecommitdiffstats
path: root/scripts/oe-buildenv-internal
Commit message (Collapse)AuthorAgeFilesLines
* oe-init-buildenv/base: Relax python version checks in favour of HOSTTOOLS ↵Richard Purdie2018-11-071-10/+1
| | | | | | | | | | | | | | manipulation Several distros are now shipping "python" as python v3 contra to the original python guidelines. This causes users confusion/pain in trying to use our tools. We can just force "python" to "python2" within HOSTTOOLS to avoid this issue and hide the complexity from the user. (From OE-Core rev: b06a6cde5c5503f456f260c773cf126085e18c8d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-env: search 'bitbake' outside of oe-coreEnrico Scholz2018-03-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | atm, 'oe-init-build-env' expects 'bitbake' to be within the OE core git repository. This complicates the project setup because you have to manage the 'bitbake' directory or symlink manually (or specify the bitbake location explicitly). Looking for 'bitbake' outside the main git repository will ease project management significantly. Now, you can put everything into git submodules, clone the project with | git clone --recursive ... and continue immediately with | ..../oe-init-build-env E.g. when you had previously | . | |-- build/ | `-- sources/ | `-- org.openembedded.core/ | `-- bitbake -> ../bitbake (where 'bitbake' must be created manually after cloning the project), you can have now | . | |-- build/ | `-- sources/ | |-- bitbake/ | `-- org.openembedded.core/ which is completely managed by 'git'. Patch adds $OEROOT/.. to the search path for 'bitbake' (From OE-Core rev: 5b3afc9cfe38a9fb435fbe5fcabc59b9a60f4657) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Fix finding build directoryRichard Purdie2017-11-051-0/+3
| | | | | | | | | | | | | | The intent of the env setup scripts is to set BBPATH to point at the build directory. This means if the user changes directory, bitbake can still find the original build directory. The default bblayers.conf files reset BBPATH to the correct components so this is safe and restores the behaviour the script was intended to have. [YOCTO #12163] (From OE-Core rev: 82eeb934997c9eaa6443079dfb649a89872a222c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env-memres: Drop itRichard Purdie2017-07-211-2/+1
| | | | | | | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: show usage outputEd Bartosh2016-12-131-0/+12
| | | | | | | | | | | | | Show usage text if script is not sourced. Tested in bash, zsh and dash. [YOCTO #10751] (From OE-Core rev: ac7a905b18acb8bd9b2412b6682afbe1d7e18d7b) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: hint at specifying bitbake path in error messagePaul Eggleton2016-08-171-1/+1
| | | | | | | | | | | | | | If you check out OE-Core and then run oe-init-build-env you get an error about not having bitbake checked out in a "bitbake" subdirectory, however it's possible to specify the bitbake path on the oe-init-build-env command line, so hint at that in the error message rather than implying it has to be in the default location. (From OE-Core rev: 5a1efa91a418e3206b047564d0fd6d5bac22a8d3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/sstate: add a mode to error if sstate package unavailablePaul Eggleton2016-07-081-1/+1
| | | | | | | | | | | | | | If BB_SETSCENE_ENFORCE is set to "1" and an sstate package fails to download outside of the whitelist specified by BB_SETSCENE_ENFORCE_WHITELIST, then fail immediately so you can tell that the problem was caused by failing to restore the task from sstate. Part of the implementation of [YOCTO #9367]. (From OE-Core rev: 9e711b54487c3141d7264b8cf0d74f9465020190) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Update to python3Richard Purdie2016-06-021-17/+21
| | | | | | | | | | | | Check that 'python' is a python v2 since that is what we assume everywhere and upstream python devs recommend. We can need both python2 and python3 available since we don't control the software we might download and run. Also check that python 3 is >= 3.4.0, our minimum version for bitbake. (From OE-Core rev: 3dd26cd6b3d731f7698f6fbcd1947969f360cdc4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: add BBPATH_EXTRA to BB_ENV_EXTRAWHITE_OERobert Yang2016-05-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | So that user can easily make their own conf files such as conf/site.conf work. For example, poky's default BBPATH in bblayers.conf is: BBPATH = "${TOPDIR}" Will change it to: BBPATH_EXTRA ??= "" BBPATH = "${BBPATH_EXTRA}${TOPDIR}" When user sets BBPATH_EXTRA in env to their own dir which contains conf/site.conf, it will work. Note, BBPATH_EXTRA must end with ":", we can't set BBPATH as "${BBPATH_EXTRA}:${TOPDIR}" since the sanity would fail when BBPATH_EXTRA is null. [YOCTO #7837] (From OE-Core rev: a3d223284854a21c84e8f6d075d23b32789afa01) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-buildenv-internal: Fix regression in BB_ENV_EXTRAWHITE settingOtavio Salvador2016-04-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The commit OE-Core:ada4639 (oe-buildenv-internal: simplify derivation of BB_ENV_EXTRAWHITE) changed the format of BB_ENV_EXTRAWHITE variable to: ,---- | BB_ENV_EXTRAWHITE='ALL_PROXY | BB_NO_NETWORK | BB_NUMBER_THREADS | ... | ' `---- Instead of: ,---- | BB_ENV_EXTRAWHITE='ALL_PROXY BB_NO_NETWORK BB_NUMBER_THREADS...' `---- The old format allow for external script parsing easier and there is no need to change the format as it has no benefit from usage perspective. (From OE-Core rev: 773e9ef9bacbf1e63fe758915d599d11762b8c1f) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: simplify derivation of BB_ENV_EXTRAWHITEAndre McCurdy2016-03-281-20/+3
| | | | | | | | | Use 'sort --unique' to combine the two lists and remove duplicates. (From OE-Core rev: ada4639f1e2952e144ea7dfb2a784181d7fcc96a) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Correct the sed expression which updates $PATHPeter Kjellerstedt2016-03-211-1/+1
| | | | | | | | | | | Without this, the code that adds paths to $PATH could cause it to end up with a trailing : which would then cause an error from the sanity checker. (From OE-Core rev: 9c200760cbbe322ed884729eb395f389c863e1c8) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Some clean upPeter Kjellerstedt2016-03-201-22/+24
| | | | | | | | | | | | | | * Consistent indentation (four spaces) * Use [ -z ...] and [ -n ... ] where possible * Unset temporary variables * Use $(...) instead of `...` * Avoid an unnecessary call to expr (From OE-Core rev: 791eec016792c3f4c04b12ae6ff93c1e23266f87) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Add variables individually to BB_ENV_EXTRAWHITEPeter Kjellerstedt2016-03-201-5/+21
| | | | | | | | | | | Instead of adding all variables to BB_ENV_EXTRAWHITE as one, treat them separately and add them one by one as needed. (From OE-Core rev: 516b63fd9dea6fcc304fca920206467d2565dede) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Add paths to $PATH individuallyPeter Kjellerstedt2016-03-201-3/+8
| | | | | | | | | | | | Instead of assuming that the path to the scripts directory always is in $PATH directly before the bitbake directory, treat them as separate paths and add them individually to $PATH. (From OE-Core rev: 5b9e91a3b1d4f56c8646d7d7937ab453cc9c40a0) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: fix return codeJuro Bystricky2015-12-221-1/+3
| | | | | | | | | | | | The script oe-buildenv-internal is called from oe-init-build-env. Make sure oe-init-buildenv does not return an error if BB_ENV_EXTRAWHITE is already set, otherwise this will cause oe-init-build-env to fail. (From OE-Core rev: 9ae79973cfdabd1b4dacddce32735c65fe3544e4) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: preserve existing BB_ENV_EXTRAWHITEJuro Bystricky2015-12-121-1/+5
| | | | | | | | | | | | | | | | | | | According to the BitBake User Manual the environment variable BB_ENV_EXTRAWHITE specifies an additional set of variables to allow through (whitelist) from the external environment into BitBake's datastore. However, running: $ source oe-init-build-env build-name will overwrite any pre-existing BB_ENV_EXTRAWHITE variables. This patch modifies this behaviour: all oe-build-internal BB_ENV_EXTRAWHITE variables are appended to any potentially already existing BB_ENV_EXTRAWHITE variables. (The variables are only appended if not already in BB_ENV_EXTRAWHITE) (From OE-Core rev: 826ae02c08b2210aa39ed51e1a9e50d40f33afb4) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-buildenv-internal: add means of skipping SDK check during setupRandy Witt2015-02-241-1/+1
| | | | | | | | | | | The oe-buildenv-internal script checks if the user is already in an sdk environment and errors if true. Add a way to skip this check. (From OE-Core rev: 6d847b84b9db2b315e17107a7ab4832d15cb2147) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Ensure error messages got to stderrRichard Purdie2013-06-181-3/+3
| | | | | | (From OE-Core rev: 631a0ec8cc7e53c2df2fc62c5276f940ed45b39e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Fix exit verses returnRichard Purdie2013-06-171-2/+2
| | | | | | | | This script is sourced so we should return, not exit. (From OE-Core rev: bde54b4c4f8de696666a8c79c8cb6cf224c246e1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/buildenv-internal/sanity: Update to python 2.7.3 as a minimumRichard Purdie2013-06-141-2/+2
| | | | | | | | | | | | We're finding bugs in python 2.6 and starting to require unittest functionality in python 2.7.x. Its time to bump the minimum version requirement. Anyone without python 2.7.x can use the buildtools-tarball out to install a standalone python/git/tar setup which will work with the system. (From OE-Core rev: 8b90f1becd40a7f857d2fbe30eaffe218a976419) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-buildenv-internal bitbake: Migrate python version checksRichard Purdie2013-06-141-0/+20
| | | | | | | | | | | In preparation for removal of the bitbake wrapper script, move the python version checks to the environment script. There are also checks within bitbake itself but these may not always function correctly on every version of python so this is really insurance. (From OE-Core rev: 07792e4a83ca4f1c8152c228813c7f795fa6a545) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Only add to $PATH if neededPeter Kjellerstedt2013-04-091-2/+3
| | | | | | | | | | | | | First strip $PATH of any existence of the paths needed by Open Embedded and BitBake. Then add the needed paths at the beginning. This makes sure the needed paths are searched first, without growing $PATH unnecessarily if oe-init-build-env is rerun for a directory for which it has previously been run. (From OE-Core rev: 7429db6f38e405774ba66b3fa1bc3ac4b74ae6b9) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Only add to $PATH if neededPeter Kjellerstedt2013-04-091-2/+3
| | | | | | | | | | | If $PATH already has the needed paths at the beginning, there is no need to add them again. This allows rerunning oe-init-build-env for the same directory without having $PATH increase unnecessarily every time. (From OE-Core rev: 161abcd3672f83990ede03d67b7388678c07150e) Signed-off-by: Peter Kjellerstedt <pkj@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add STAMPS_DIR for constructing STAMPRobert Yang2013-03-071-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | Add STAMPS_DIR for constructing STAMP, the defination of STAMP is: STAMP = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" We can only change the TMPDIR if we want to change the STAMP's location, but the bb_cache.dat would be regenerated if TMPDIR changes, so add STAMPS_DIR for constructing it, and add it to the BB_ENV_EXTRAWHITE, this is very usefull for the "bitbake -S", since then it can be run by: STAMPS_DIR=<path> bitbake -S <recipe> which will avoid putting the stamps to ${TMPDIR}/stamps. BTW, break the too long BB_ENV_EXTRAWHITE into several lines. [YOCTO #1659] (From OE-Core rev: ce732c04b3ac06633e20efa8799c4189abfd41b3) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Add upper and lower case proxy vars to BB_ENV_EXTRAWHITEDarren Hart2013-02-111-1/+1
| | | | | | | | | | | | | | | | | Applications are inconsistent in their use of upper and lower case proxy variables. Curl, for example, specifies NO_PROXY (not no_proxy) in the man page (changed in 2009 [1]). Avoid proxy issues by ensuring both the upper and lower case versions of each proxy variable are available in the environment for the fetcher commands. Add FTPS_PROXY and ftps_proxy to the list as well. 1. http://curl.haxx.se/mail/tracker-2009-04/0012.html (From OE-Core rev: 684c6512850ceb108e52af634be98eaacb8351e1) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Remove GIT variables from BB_ENV_EXTRAWHITEDarren Hart2013-02-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following variables perform no function outside of bitbake: GIT_CONFIG GIT_PROXY_HOST GIT_PROXY_PORT GIT_PROXY_IGNORE GIT_CONFIG only affects the git-config command which is not relevant to the fetcher. This was previously used with the OE GIT_CORE_CONFIG variable which would provide a basic git config to use instead of the user's config. This usage was deprecated by git for over a year now: http://git.661346.n2.nabble.com/Overriding-gitconfig-using-GIT-CONFIG-td6680977 GIT_PROXY_HOST and GIT_PROXY_PORT are not used by git. GIT_PROXY_IGNORE was an OE construct used to create the custom git config and had no meaning outside of the OE environment. It is not used by git. Remove these variables from the fetcher environment. Users wishing to configure git to work with a proxy should define the GIT_PROXY_COMMAND environment variable to use an external script. NO_PROXY can be used within this script to skip the proxy for certain hosts. (From OE-Core rev: ea0284a8cc1b531e115b7fdbfa18852f55573f00) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Add BB_NO_NETWORK to BB_ENV_EXTRAWHITEOtavio Salvador2012-10-071-1/+1
| | | | | | | | | | This allows for use of bitbake in offline mode, but override it in command line. (From OE-Core rev: bcefd015fb163d9c382ae05a86569dbcfd3d736a) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-buildenv-internal: Ensure we detect the SDK/ADT and error outRichard Purdie2012-10-021-0/+5
| | | | | | | | | | | | | | The SDK/ADT may ship with a python installed which may not have all the modules need for a bitbake build. We should therefore detect if its already present in the environment and error out in this case, asking the user to use a clean environment. This also removes the potential for any other conflict between the two. [YOCTO #2979] (From OE-Core rev: 9496d4cd77ae632251b4262b63be857fc4fcb31e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Fix BITBAKEDIR changes to work with existing ↵Richard Purdie2012-05-121-3/+4
| | | | | | | | | | | | autobuilder scritpts The BITBAKEDIR change does not work well when the script is sourced from another script since $2 may be unrelated. This change adds the logic onto the BDIR conditional and which more external scripts would set, hence avoiding the problem. (From OE-Core rev: ec8fbe0d1870285a4a972ddcfe83aa63d720cb80) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add option to oe-buildenv-internal script to change bitbake location.Philip Balister2012-05-111-1/+5
| | | | | | | | | | | | | | | | Having bitbake inside the oe-core is annoying to some people. This commit adds a second option to the oe-init-build-env script. Run like this: . ./oe-init-build-env ../build ../bitbake for example. Without the second option, the old behavior is preserved. (From OE-Core rev: 45510a0dd7a9321c29c5b21ac4053192f7ab9ad5) Signed-off-by: Philip Balister <philip@balister.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* terminal.bbclass, oe-buildenv-internal: pass SCREENDIR environment variableJason Wessel2012-05-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some versions of the screen utility provided from the host OS vendor write the socket directory to $HOME/.screen. When using a shared home directory across many servers, one sets the SCREENDIR environment variable to avoid collisions in the shared home directory. This results in problems launching a devshell where it is not entirely obvious what happened because the SCREENDIR environment variable got stripped from the environment prior to setting up the screen in detached mode. Example: % bitbake -c devshell busybox # ...Please connect in another terminal with "screen -r devshell" % screen -r devshell There is no screen to be resumed matching devshell. The temporary work around was to do something like: sh -c "unset SCREENDIR; screen -r devshell" This patch adds SCREENDIR to the white list to ensure screen works properly on systems where a developer needs to use the SCREENDIR with shared home directories. (From OE-Core rev: 5568a8f5a1c65bae021b2e36d735d3153acc6d72) 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". (From OE-Core rev: 17e981a857a51b0bec08c929e8539d36d83874b6) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-buildenv-internal: Add SOCKS5_{USER, PASSWD} to BB_ENV_EXTRAWHITEKumar Gala2011-10-061-2/+1
| | | | | | | | | | | | | | | | | If a SOCKS5 gateway is needed for a proxy access like git it might also require authentication to the proxy via a password and username. Adding SOCKS5_USER & SOCKS5_PASSWD to BB_ENV_EXTRAWHITE allow for automation of the authentication request to occur when something like a git fetch is going through the proxy. This patch requires the bitbake patch to add extra exportvars so these variables get passed from Env -> bitbake -> fetcher (From OE-Core rev: 9206ea0f7cd39d2ba6ff4b41cbeb17409d3ae5f1) Signed-off-by: Kumar Gala <galak@kernel.crashing.org> Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-buildenv-internal: improve the error detecting for $BDIRDexuan Cui2011-08-101-8/+15
| | | | | | | | | | | | | | | | The previous fix for a bug in Ubuntu 10.04 readlink, be2a2764d8ceb398d81714661e6f199c8b11946c, notified the user when a trailing slash was used. As there is no semantic difference, simply remove any trailing slashes and proceed without nagging the user. See [YOCTO #671] for more details. (From OE-Core rev: 074ca832c0274e0e92698b4d006ef2708be105b8) Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Acked-by: Darren Hart <dvhart@linux.intel.com> Cc: Paul Eggleton <paul.eggleton@linux.intel.com> 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-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | [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. (From OE-Core rev: 651ccb3b031d9ccb8331505a51171372002230d9) Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Replace POKYMODE POKYLIBC with TCMODE and TCLIBCKhem Raj2011-07-191-1/+1
| | | | | | | | | These are new variable names in oe-core (From OE-Core rev: edbda3e188ba1eac36a49e66e3751d873aba4583) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add PARALLEL_MAKE to BB_ENV_EXTRAWHITEDarren Hart2011-06-281-1/+1
| | | | | | | | | | | | As BB_NUMBER_THREADS is already whitelisted, it is consistent to also allow PARALLEL_MAKE to be overridden via the environment. This also simplifies performance testing where multiple combinations of those two variables are a natural thing to do. (From OE-Core rev: 8a89a2e641fd5fa97a7d6977f55d10790ee13d58) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/oe-buildenv-internal: Improve message when bitbake is missingRichard Purdie2011-05-181-1/+1
| | | | | | | (From OE-Core rev: b4391b6b8c14a9779b44c9909e6a7cac1ee351e6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Further cleanup of various poky referencesRichard Purdie2011-04-211-3/+3
| | | | | | (From OE-Core rev: fe73ea8c510877fe4e3c117985e8f3d0b79ddf1b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename poky-qemu to runqemuRichard Purdie2011-04-211-1/+1
| | | | | | (From OE-Core rev: 7687d91f73f4a116593315b3b1488ac3f0904905) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename poky-init-build-env to oe-init-build-envRichard Purdie2011-04-211-0/+58
(From OE-Core rev: fa6176219b741eed346b21a3d923e9abc9b5442a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-05 19:02:17 +0000