On Sun, 2019-09-08 at 20:16 -0700, Khem Raj wrote: > This helps recipes where they need to explicitly pass the variable > and > does not entertain the ones from environment > > Signed-off-by: Khem Raj <[email protected]> > --- > meta/classes/python3native.bbclass | 6 ++++-- > meta/classes/pythonnative.bbclass | 6 ++++-- > 2 files changed, 8 insertions(+), 4 deletions(-) > > diff --git a/meta/classes/python3native.bbclass > b/meta/classes/python3native.bbclass > index d98fb4c758..bed04bd941 100644 > --- a/meta/classes/python3native.bbclass > +++ b/meta/classes/python3native.bbclass > @@ -14,8 +14,8 @@ export STAGING_LIBDIR > # find_package(PythonLibs REQUIRED) > # which ends up using libs/includes from build host > # Therefore pre-empt that effort > -export > PYTHON_LIBRARY="${STAGING_LIBDIR}/lib${PYTHON_DIR}${PYTHON_ABI}.so" > -export > PYTHON_INCLUDE_DIR="${STAGING_INCDIR}/${PYTHON_DIR}${PYTHON_ABI}" > +PYTHON_LIBRARY="${STAGING_LIBDIR}/lib${PYTHON_DIR}${PYTHON_ABI}.so" > +PYTHON_INCLUDE_DIR="${STAGING_INCDIR}/${PYTHON_DIR}${PYTHON_ABI}" > > export _PYTHON_SYSCONFIGDATA_NAME="_sysconfigdata" > > @@ -24,3 +24,5 @@ export PYTHONNOUSERSITE = "1" > > # autoconf macros will use their internal default preference > otherwise > export PYTHON > +export PYTHON_LIBRARY > +export PYTHON_INCLUDE_DIR
I'm confused as this makes no difference to bitbake and is equivalent. exported variables are always set in the datastore... Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
