Make indentation consistent here in preparation for the changes that
follow.

Signed-off-by: Paul Eggleton <[email protected]>
---
 meta/classes/populate_sdk_ext.bbclass | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/classes/populate_sdk_ext.bbclass 
b/meta/classes/populate_sdk_ext.bbclass
index c244d93..90033ba 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -238,11 +238,11 @@ sdk_ext_postinst() {
        mv *-nativesdk-libc.tar.* $target_sdk_dir/`dirname 
${oe_init_build_env_path}`
 
        if [ "$prepare_buildsystem" != "no" ]; then
-           printf "Preparing build system...\n"
-           # 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* > 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 ; }
+               printf "Preparing build system...\n"
+               # 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* > 
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 ; }
        fi
        echo done
 }
-- 
2.1.0

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to