toolchain-scripts.bbclass: Use PYTHONPATH instead of PYTHONHOME
In the extensible sdk it was originally intended that the native sstate would always be setscened as part of the sdk installation. However, the soon to come "minimal" sdk won't do that. A side effect of that is that pointing PYTHONHOME at the native sysroot within the "bitbake workspace" won't work. For now only set PYTHONPATH instead and continue using the python that comes from buildtools. (From OE-Core rev: 81f126f4a8944e395f3909de2317065c09b04b5e) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
f1f8447750
commit
5b7a43e85e
|
@ -31,7 +31,7 @@ toolchain_create_sdk_env_script () {
|
|||
echo "export OECORE_NATIVE_SYSROOT=\"$sdkpathnative\"" >> $script
|
||||
echo 'export OECORE_TARGET_SYSROOT="$SDKTARGETSYSROOT"' >> $script
|
||||
echo "export OECORE_ACLOCAL_OPTS=\"-I $sdkpathnative/usr/share/aclocal\"" >> $script
|
||||
echo "export PYTHONHOME=$sdkpathnative$prefix" >> $script
|
||||
echo "export PYTHONPATH=$sdkpathnative$prefix" >> $script
|
||||
echo 'unset command_not_found_handle' >> $script
|
||||
|
||||
toolchain_shared_env_script
|
||||
|
|
Loading…
Reference in New Issue