openembedded-core.git/meta/classes/cross-canadian.bbclass, branch fido

cross-canadian/meta-environment: Allow modification of TARGET_OS to be optional

2015-01-16T09:13:44+00:00

There are some cases we want the manipulation cross-canadian performance
on TARGET_OS, there are also cases like meta-environment where we do not
want this manipulation.

We did try and use immediate expansion to avoid this problem and it
works in the non multilib case. If we have a multilib that used an
extension, like for example:

require conf/multilib.conf
MULTILIBS = "multilib:lib32 multilib:lib64"
DEFAULTTUNE = "mips32r2"
DEFAULTTUNE_virtclass-multilib-lib32 = "mips64-n32"
DEFAULTTUNE_virtclass-multilib-lib64 = "mips64"

then the n32 extension case will be misconfigured.

It turns out saving an unexpanded variable is hard. The best I could
come up with was:

SAVEDTOS := "${@d.getVar('TARGET_OS', False).replace("{", "*")}"

and then

localdata.setVar("TARGET_OS", d.getVar("SAVEDOS", False).replace('*','{'))

which is rather evil, I'd challenge someone to come up with a nicer way
of making it work though!

Rather than the above madness, we modify cross-canadian to make the
problamtic code conditional.

This fixes the original issue (where a linux-gnuspe target was seeing
'linux') of
http://cgit.openembedded.org/openembedded-core/commit/?id=0038634ee6e2b6035c023a2702547f20f67c103a
but also fixes the multilib one.

Signed-off-by: Richard Purdie

cross-canadian: Disable the packagedata stamp-extra-info

2014-10-06T14:07:39+00:00

Similarly to native/cross disable this since otherwise the packagedata
can be marked as machine specific and if you switch machines
which share an architecture, you'll get toolchain overlapping files
errors.

Signed-off-by: Richard Purdie

cross-canadian: Copy target_ definitions from cross.bbclass

2014-07-25T14:33:32+00:00

A while back we fixed the cross definitions to work better in multilib
configurations, apply the same fixes to cross-candian.bbclass

Signed-off-by: Richard Purdie

cross-canadian: Fix shlibs directory after recent shlibs changes

2014-07-17T11:27:02+00:00

Signed-off-by: Richard Purdie

cross-canadian.bbclass: Recognise musl

2014-05-30T15:31:22+00:00

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

binutils/gcc/gdb: Add TARGET_ARCH to PN for all cross recipes

2014-04-30T15:33:26+00:00

This allows them to co-exist together in the native sysroot, with one
set of cross tools per target architecture.

Signed-off-by: Richard Purdie

cross-canadian: Let cross-canadian packages build for uclibc

2013-11-08T17:27:14+00:00

Fixes errors like

Parsing recipes...ERROR: Building cross-candian powerpc for an unknown
TARGET_SYS (powerpc-angstrom-linux-uclibc), please update
cross-canadian.bbclass
ERROR: Building cross-candian powerpc for an unknown TARGET_SYS
(powerpc-angstrom-linux-uclibc), please update cross-canadian.bbclass

Signed-off-by: Khem Raj 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

cross-canadian: Improve comment

2013-10-30T18:00:56+00:00

The previous cross-canadian change was missing some tweaks
to the comments. This clarifies them slightly.

Signed-off-by: Richard Purdie

cross-canadian: Handle powerpc linux verses linux-gnuspe

2013-10-30T17:33:00+00:00

PowerPC toolchains can use the OS "linux" or "linux-gnuspe". This
patch links them together so the one cross-canadian toolchain can support
both.

GCC_FOR_TARGET is set for the GCC recipe as otherwise configure
can pick up an incorrect value.

[YOCTO #5354]

Signed-off-by: Richard Purdie 
Signed-off-by: Saul Wold

cross-canadian: Fix SHLIBSDIR when using multilib

2013-10-16T12:27:56+00:00

Both nativesdk and multilib use MLPREFIX for their partciular purposes. When
we have both set, cross-canadian can confuse SHLIBSDIR. This forces the
variable to the correct value for cross-canadian, fixing toolchains in
multilib builds.

[YOCTO #5333]

Signed-off-by: Richard Purdie