]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commit
oe-buildenv-internal: remove path from previous project
authorChen Qi <Qi.Chen@windriver.com>
Mon, 15 May 2023 04:53:35 +0000 (12:53 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 22 May 2023 09:53:44 +0000 (10:53 +0100)
commit3405a3221b8f6641a8e42b04bc7acd6e032aeab8
tree40867c5d0e92a0177ec492208abbba312376bc1f
parent09ac564539a2bea835bdb8aee022505fc4b391f8
oe-buildenv-internal: remove path from previous project

Util now, only paths added for current project are removed
to avoid PATH growing unnecessarily. This is to handle the case
of sourcing the init script into different build directories.

However, if we source the init script from different projects into
different build directories, the paths added by previous projects
are not cleaned up.

To avoid this, we record the paths added into OE_ADDED_PATHS, and
remove it in the next sourcing.

The OE_ADDED_PATHS variable is exported mainly for the two reasons:
1. users can clearly see it in the `env' command's output.
2. if the prefixed PATH is carried into the subprocess (e.g., a subshell),
   so should this OE_ADDED_PATHS variable that prefixes it.

Note that the paths, "$OEROOT/scripts:$BITBAKEDIR/bin:", are added
as a whole. A previous commit, "oe-buildenv-internal: Add paths to $PATH individually",
made the change to treat these two paths separately, the reason was
not "assuming the path to the scripts directory always is in $PATH
directly before the bitbake directory". But this is exactly the effect
of the codes. I see no reason why we should complicate things.

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
scripts/oe-buildenv-internal