]> code.ossystems Code Review - openembedded-core.git/commit
oe-init-build-env*: Allow $OEROOT to be predefined
authorPeter Kjellerstedt <pkj@axis.com>
Tue, 15 Mar 2016 14:41:02 +0000 (15:41 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Sun, 20 Mar 2016 22:57:58 +0000 (22:57 +0000)
commit3327e2a9222004d8ac7974cb1d9fe77c81176cfc
treeabaaa512adf3302e9f6aa6d6e8846fcb167dd0aa
parent75c5dc8d4a5506bf5b89292a96c7b9f91e9d71c8
oe-init-build-env*: Allow $OEROOT to be predefined

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>
oe-init-build-env
oe-init-build-env-memres