[oe-commits] [openembedded-core] 14/65: classes/populate_sdk_ext: prepend to PATH rather than appending

[git at git.openembedded.org]

rpurdie pushed a commit to branch master-next
in repository openembedded-core.

commit 034951da45ca9a0a573e55043e24b6700b5c2a25
Author: Paul Eggleton <paul.eggleton at linux.intel.com>
AuthorDate: Tue Mar 1 00:50:53 2016 +1300

    classes/populate_sdk_ext: prepend to PATH rather than appending
    
    The rest of the environment setup script prepends to PATH, so when we
    add the path to run devtool we should be prepending as well. This
    also ensures that when you run the environment setup script from
    extensible SDK installation A and then in the same shell session run the
    environment setup script from installation B, and then run devtool, that
    you're running B's devtool and not A's.
    
    Fixes [YOCTO #9046].
    
    Signed-off-by: Paul Eggleton <paul.eggleton at linux.intel.com>
    Signed-off-by: Ross Burton <ross.burton at intel.com>
---
 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 9e2fc61..27d4afc 100644
--- a/meta/classes/populate_sdk_ext.bbclass
+++ b/meta/classes/populate_sdk_ext.bbclass
@@ -323,7 +323,7 @@ sdk_ext_postinst() {
 
 	# A bit of another hack, but we need this in the path only for devtool
 	# so put it at the end of $PATH.
-	echo "export PATH=\$PATH:$target_sdk_dir/sysroots/${SDK_SYS}/${bindir_nativesdk}" >> $env_setup_script
+	echo "export PATH=$target_sdk_dir/sysroots/${SDK_SYS}${bindir_nativesdk}:\$PATH" >> $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
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.