]> code.ossystems Code Review - openembedded-core.git/commitdiff
populate_sdk_ext: Log the "Preparing build system" step
authorRandy Witt <randy.e.witt@linux.intel.com>
Wed, 25 Mar 2015 00:16:26 +0000 (17:16 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 31 Mar 2015 21:21:45 +0000 (22:21 +0100)
When using bitbake to do the setscene as part of sdk setup, it would be
useful to have a log in the case where it fails.

The log is called preparing_build_system.log and is in the top level
directory of the extracted sdk.

Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/populate_sdk_ext.bbclass

index ec1cff06583b7d3e8412c0b9859b78f0d588b552..22e0ffca28b0c2b0bdb3a9f85ce3ee8549d84e90 100644 (file)
@@ -182,7 +182,7 @@ sdk_ext_postinst() {
        # dash which is /bin/sh on Ubuntu will not preserve the
        # current working directory when first ran, nor will it set $1 when
        # sourcing a script. That is why this has to look so ugly.
-       sh -c ". buildtools/environment-setup* > /dev/null && cd $target_sdk_dir/`dirname ${oe_init_build_env_path}` && set $target_sdk_dir && . $target_sdk_dir/${oe_init_build_env_path} $target_sdk_dir > /dev/null && bitbake ${SDK_TARGETS} > /dev/null" || { echo "SDK preparation failed" ; exit 1 ; }
+       sh -c ". buildtools/environment-setup* > preparing_build_system.log && cd $target_sdk_dir/`dirname ${oe_init_build_env_path}` && set $target_sdk_dir && . $target_sdk_dir/${oe_init_build_env_path} $target_sdk_dir >> preparing_build_system.log && bitbake ${SDK_TARGETS} >> preparing_build_system.log" || { echo "SDK preparation failed: see `pwd`/preparing_build_system.log" ; exit 1 ; }
        echo done
 }