linux/poky.git/scripts/oe-buildenv-internal, branch 1.3_M4

oe-buildenv-internal: Fix BITBAKEDIR changes to work with existing autobuilder scritpts

2012-05-12T07:43:15+00:00

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

Add option to oe-buildenv-internal script to change bitbake location.

2012-05-11T22:24:03+00:00

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 Signed-off-by: Richard Purdie

terminal.bbclass, oe-buildenv-internal: pass SCREENDIR environment variable

2012-05-06T08:55:46+00:00

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

Various typoes fixed, all comments or output strings.

2012-03-26T11:13:05+00:00

Typoes fixed: "enviroment", "editted", "spliting", "scheulder". (From OE-Core rev: 17e981a857a51b0bec08c929e8539d36d83874b6) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie

scripts/oe-buildenv-internal: Add SOCKS5_{USER, PASSWD} to BB_ENV_EXTRAWHITE

2011-10-06T15:59:40+00:00

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 Signed-off-by: Matthew McClintock Signed-off-by: Richard Purdie

scripts/oe-buildenv-internal: improve the error detecting for $BDIR

2011-08-10T12:33:06+00:00

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 Acked-by: Darren Hart Cc: Paul Eggleton Signed-off-by: Richard Purdie

oe-init-build-env, scripts/oe-buildenv-internal: add error detecting for $BDIR

2011-08-02T13:32:10+00:00

[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 Signed-off-by: Richard Purdie

oe-buildenv-internal: Replace POKYMODE POKYLIBC with TCMODE and TCLIBC

2011-07-19T16:34:19+00:00

These are new variable names in oe-core (From OE-Core rev: edbda3e188ba1eac36a49e66e3751d873aba4583) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

Add PARALLEL_MAKE to BB_ENV_EXTRAWHITE

2011-06-28T14:06:53+00:00

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 Signed-off-by: Richard Purdie

scripts/oe-buildenv-internal: Improve message when bitbake is missing

2011-05-18T11:42:26+00:00

(From OE-Core rev: b4391b6b8c14a9779b44c9909e6a7cac1ee351e6) Signed-off-by: Richard Purdie Signed-off-by: Richard Purdie