Because this is disabled when SDK tests (compatibility) ran using eSDK so sometimes needs to SILENT it when automatic process is working another times don't like when user uses it. In this case the SDK tests fails because it looks to stdout and found devtool msg. alimon On 02/02/2016 03:19 PM, Paul Eggleton wrote: > On Tue, 02 Feb 2016 09:14:18 Aníbal Limón wrote: >> From: Aníbal Limón >> >> Sometimes we need to load environment without show help information >> only useful when user is interacting with the SDK. >> >> For example: For test extensible SDK. >> >> Signed-off-by: Aníbal Limón >> --- >> meta/classes/populate_sdk_ext.bbclass | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/meta/classes/populate_sdk_ext.bbclass >> b/meta/classes/populate_sdk_ext.bbclass index 76308ec..fc96a4b 100644 >> --- a/meta/classes/populate_sdk_ext.bbclass >> +++ b/meta/classes/populate_sdk_ext.bbclass >> @@ -291,7 +291,7 @@ sdk_ext_postinst() { >> # so put it at the end of $PATH. >> echo "export >> PATH=\$PATH:$target_sdk_dir/sysroots/${SDK_SYS}/${bindir_nativesdk}" >> >> $env_setup_script >> >> - echo "printf 'SDK environment now set up; additionally you may now run >> devtool to perform development tasks.\nRun devtool --help for further >> details.\n'" >> $env_setup_script + echo "[ -z \$OE_SDK_EXT_SILENT ] && >> printf 'SDK environment now set up; additionally you may now run devtool to >> perform development tasks.\nRun devtool --help for further details.\n'" >> >> $env_setup_script >> >> # Warn if trying to use external bitbake and the ext SDK together >> echo "(which bitbake > /dev/null 2>&1 && echo 'WARNING: attempting to use >> the extensible SDK in an environment set up to run bitbake - this may lead >> to unexpected results. Please source this script in a new shell session >> instead.') || true" >> $env_setup_script > > Rather than adding another variable for this why not just redirect the output > to /dev/null ? > > Cheers, > Paul >