[OE-core] [PATCH] oe-buildenv-internal: Fix finding build directory

Otavio Salvador otavio.salvador at ossystems.com.br
Tue Oct 31 23:25:40 UTC 2017


On Tue, Oct 31, 2017 at 9:16 PM, Burton, Ross <ross.burton at intel.com> wrote:
> On 21 October 2017 at 13:06, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
>>
>> The intent of the env setup scripts is to set BBPATH to point at the
>> build directory if not already set. This means if the user changes
>> directory, bitbake can still find the original build directory. The
>> default bblayers.conf files reset BBPATH to the correct components so
>> this is safe and restores the behaviour the script was intended to have.
>>
>> [YOCTO #12163]
>>
>> Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
>> ---
>>  scripts/oe-buildenv-internal | 5 +++++
>>  1 file changed, 5 insertions(+)
>>
>> diff --git a/scripts/oe-buildenv-internal b/scripts/oe-buildenv-internal
>> index e6cd141..abc5aff 100755
>> --- a/scripts/oe-buildenv-internal
>> +++ b/scripts/oe-buildenv-internal
>> @@ -105,6 +105,11 @@ fi
>>
>>  BITBAKEDIR=$(readlink -f "$BITBAKEDIR")
>>  BUILDDIR=$(readlink -f "$BUILDDIR")
>> +if [ -z "$BBPATH" ]; then
>> +    BBPATH=$BUILDDIR
>> +fi
>> +
>> +export BBPATH
>
>
> This breaks the use-case of the user switching between build directories as
> re-executing oe-init-build-env doesn't change BBPATH.

I know and that's why I asked for a warning! ;-)

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750



More information about the Openembedded-core mailing list