On Thursday 09 October 2014 18:53:13 Otavio Salvador wrote: > Sometimes we require extra environment settings to be available on the > environment for proper SDK work. This were done, in past, using > '_append' tasks however with the split of the environment in a > canadian package this has been broken. > > The easier and more flexible solution is to use environment subscripts > which are sources by the main script. These are now looked at: > > $OECORE_NATIVE_SYSROOT/environment-setup.d/*.sh > > and sourced. > > Signed-off-by: Otavio Salvador <[email protected]> > --- > meta/classes/toolchain-scripts.bbclass | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/meta/classes/toolchain-scripts.bbclass > b/meta/classes/toolchain-scripts.bbclass index 6cc8eba..11ffbe5 100644 > --- a/meta/classes/toolchain-scripts.bbclass > +++ b/meta/classes/toolchain-scripts.bbclass > @@ -72,6 +72,16 @@ toolchain_shared_env_script () { > echo 'export OECORE_SDK_VERSION="${SDK_VERSION}"' >> $script > echo 'export ARCH=${ARCH}' >> $script > echo 'export CROSS_COMPILE=${TARGET_PREFIX}' >> $script > + > + cat >> $script <<EOF > + > +# Append environment subscripts > +if [ -d "\$OECORE_NATIVE_SYSROOT/environment-setup.d" ]; then > + for envfile in \$OECORE_NATIVE_SYSROOT/environment-setup.d/*.sh; do > + source \$envfile > + done > +fi > +EOF > } > > #we get the cached site config in the runtime
This series looks great to me, and adds a much better extension mechanism than we've had here previously. Acked-by: Paul Eggleton <[email protected]> -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
