| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
(From OE-Core rev: 3ef80db73c69b8a731beb8ea4921357a041564e5)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
| |
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 <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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 <mark.hatle@windriver.com>
|
| |
|
|
|
|
|
|
|
|
| |
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 <mark.hatle@windriver.com>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
<<later, in a different shell>>
$ 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 <josh@linux.intel.com>
|
| |
|
|
| |
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
| |
|
|
|
|
|
|
|
|
| |
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 <joe@deserted.net>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
| |
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@2227 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1734 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
|
|
| |
scripts/poky-env-internal. Add poky-autobuild script for autobuilder use.
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@948 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
|
|
| |
OEROOT, add BUILD_SYS variable
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@866 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
|
|
| |
request.
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@671 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@668 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
|
|
| |
conf/site.conf for settings common to all build dirs. unset TERMINFO to avoid glibc pulling in the user's terminal information files.
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@667 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
|
|
| |
local.conf, and set TMPDIR explicitly to avoid the requirement that one run bitbake from the build directory.
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@650 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@553 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
| |
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@541 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@537 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
