openembedded-core.git/poky-init-build-env, branch master

Rename poky-init-build-env to oe-init-build-env

2011-04-20T14:59:04Z

Signed-off-by: Richard Purdie

poky-init-build-env: unbork for zsh

2011-03-21T17:49:17Z

Signed-off-by: Chris Larson

poky-init-build-env: unset BBPATH

2011-01-18T00:20:21Z

When using OpenEmbedded and Yocto I had it previously set to OE and this made bitbake to get confused. This was difficult to figure out and then it seems safer and cleaner if the script unset it to avoid this confusing behaviour. Signed-off-by: Otavio Salvador Signed-off-by: Richard Purdie

poky-init-build-env: Enable all POSIX shells

2010-12-20T23:00:51Z

Update the script so that it will work in more then just bash. If bash is not used, it will assume the PWD is the Poky location. (This is because BASH_SOURCE is a bash-ism, and equivalent functionality is not available in other shells). This has been verified with dash (see comment in the code), ksh, zsh and of course bash. Signed-off-by: Mark Hatle

poky-init-build-env: Breakup the environment script

2010-12-20T23:00:25Z

Break up the scripts/poky-env-internal into two parts: 1) Chunk that is sourced and sets up the environment 2) Chunk that is executed and configures the build directory OEROOT configuration was moved into the initial poky-init-build-env script. Signed-off-by: Mark Hatle

poky-init-build-env: Fix to show the error message with simple sh based shells

2010-11-13T14:26:46Z

Signed-off-by: Richard Purdie

Enable build dir outside of the poky directory

2010-07-21T14:39:53Z

You need to first set up the build directory by sourcing the poky build script, after that builds can be run in that directory so long as bitbake is in $PATH removing the need to source the init script for each build. i.e: $ . poky-init-build-env ~/my-build $ bitbake some-image <> $ cd ~/my-build $ export PATH=/path/to/bitbake/bin:$PATH $ bitbake an-image This patch also removes use of OEROOT in recipes, etc. Signed-off-by: Joshua Lock

poky-init-build-env: Remove now unneeded return

2009-11-26T11:25:16Z

Signed-off-by: Richard Purdie

poky-init-build-env: Update for BASH 4 Bourne Shell semantics

2009-11-12T16:49:45Z

It's no longer valid in bash 4 when invoked with Bourne Shell semantics to return unless you're inside a sourced script or a function. Doing so in this context doesn't actually exit from the setup script. This should probably preserve the original intent. Signed-off-by: Joe MacDonald Signed-off-by: Richard Purdie

poky-init-build-env: Don't exit from sourced scripts, return

2007-07-25T10:44:56Z

git-svn-id: https://svn.o-hand.com/repos/poky/trunk@2227 311d38ba-8fff-0310-9ca6-ca027cbcb966