All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE scons cross-compile patch
Date: Sun, 12 Feb 2012 00:48:35 +0100	[thread overview]
Message-ID: <jh6uoh$nnj$1@dough.gmane.org> (raw)
In-Reply-To: <CAHQecY5ARQUHqUScJqReFO_mD3t_U-ViMYQrS=Rox-xoGR3k-A@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Shouldn't these go to the oe-core list?

Op 12-02-12 00:24, Tom King schreef:
> ---------- Forwarded message ---------- From: S. Lockwood-Childs
> <sjl@vctlabs.com> Date: Sat, Feb 11, 2012 at 4:03 PM Subject: OE scons
> cross-compile patch To: ka6sox@gmail.com
> 
> 
> commit 9f66f474614696154d50156ada5f4c**1629b1b28c Author: S
> Lockwood-Childs <sjl@vctlabs.com> Date:   Sat Feb 11 15:07:17 2012 -0800
> 
> cross-compile support for SCons
> 
> scons build system searches paths for hard-coded tool names like "gcc", 
> so this patch teaches it to check first for a tool with cross-compile 
> prefix if the CROSS_COMPILE variable has been set. If not found, it falls
> back to searching for the un-prefixed tool name.
> 
> For example, if CROSS_COMPILE=arm-angstrom-**linux-gnueabi- 
> SCons.Evironment.Detect('gcc') should find
> arm-angstrom-linux-gnueabi-gcc SCons.Evironment.Detect('zip') should find
> plain zip
> 
> diff --git
> a/meta/recipes-devtools/**python/python-scons-native/**scons-cross-toolchain.patch
>
> 
b/meta/recipes-devtools/**python/python-scons-native/**
> scons-cross-toolchain.patch new file mode 100644 index 0000000..041279e 
> --- /dev/null +++
> b/meta/recipes-devtools/**python/python-scons-native/** 
> scons-cross-toolchain.patch @@ -0,0 +1,17 @@ +---
> scons-2.1.0/engine/SCons/**Environment.py.orig       2012-02-10 
> 16:59:10.000000000 -0800 ++++ scons-2.1.0/engine/SCons/**Environment.py
> 2012-02-11 13:29:15.000000000 -0800 +@@ -1483,6 +1483,14 @@ +         if
> not SCons.Util.is_List(progs): +             progs = [ progs ] +
> for prog in progs: ++            # prefer cross version of program, if it
> exists ++            if 'CROSS_COMPILE' in self._dict: ++
> cross_prog = self['CROSS_COMPILE'] + prog ++                #print
> "Looking for %s" % cross_prog ++                path =
> self.WhereIs(cross_prog) ++                if path: return cross_prog ++ 
> ++            #print "Looking for %s" % prog +             path =
> self.WhereIs(prog) +             if path: return prog +         return
> None diff --git
> a/meta/recipes-devtools/**python/python-scons-native_2.**1.0.bb<http://python-scons-native_2.1.0.bb>b/meta/recipes-devtools/
>
> 
**python/python-scons-native_2.**1.0.bb<http://python-scons-native_2.1.0.bb>
> index ff94cf6..c653237 100644 ---
> a/meta/recipes-devtools/**python/python-scons-native_2.**1.0.bb<http://python-scons-native_2.1.0.bb>
>
> 
+++
b/meta/recipes-devtools/**python/python-scons-native_2.**1.0.bb<http://python-scons-native_2.1.0.bb>
> @@ -2,4 +2,6 @@ require python-scons_${PV}.bb inherit native DEPENDS =
> "python-native" RDEPENDS_${PN} = "" -PR = "r1" +PR = "r2" + +SRC_URI +=
> "file://scons-cross-toolchain.**patch"
> 
> 
> 
> _______________________________________________ Openembedded-devel
> mailing list Openembedded-devel@lists.openembedded.org 
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk82/lEACgkQMkyGM64RGpG8OQCfcZk0EZs2iyyTwnJsAxpFOZvm
z+EAoJlGm6KD41LyaFpN3hgMQC3LDitY
=Lp55
-----END PGP SIGNATURE-----




  reply	other threads:[~2012-02-11 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.1202111600300.3065@www.vctlabs.com>
2012-02-11 23:24 ` OE scons cross-compile patch Tom King
2012-02-11 23:48   ` Koen Kooi [this message]
2012-02-12 20:05 ` Tom King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='jh6uoh$nnj$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.