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

cross-canadian.bbclass: big-endian ARM is also gnueabi.

2015-09-29T14:15:48+00:00

If building for a BE8 ARM target, arch is "armeb" rather than
"arm", but ABI should still be "gnueabi". Otherwise gcc won't
build.

Signed-off-by: Peter Seebach 
Signed-off-by: Richard Purdie

cross-canadian.bbclass: typo fix in comments (s/repsonsible/responsible/)

2015-09-06T14:24:27+00:00

Signed-off-by: Mario Domenech Goulart 
Signed-off-by: Richard Purdie

cross-canadian.bbclass: support for TCLIBC="baremetal"

2015-08-30T11:34:11+00:00

Allow "baremetal" builds.

(From OE-Core rev: 0cd3121058ea620c74622f1200c8040696b4d1d8)

Signed-off-by: Juro Bystricky 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

cross-canadian/gcc: Various mips64 fixes

2015-07-31T14:15:13+00:00

"n32" is a mips64 variant we need to consider when processing the TARGET_OS
extensions. Also add the multilib extensions for mips64.

Signed-off-by: Richard Purdie

cross-canadian: Add symlinks for multilib cases

2015-07-31T14:15:12+00:00

In the same way we map various TARGET_OS options back to the single
cross-canadian compiler, add mappings for the TARGET_VENDOR cases we
know about in the multilib case.

Signed-off-by: Richard Purdie

cross-canadian: Put links in place for uclibc and musl

2015-07-27T22:28:22+00:00

gcc-cross-canadian- is only built once. It needs to target all the
different libcs, not just the currently selected one. This change
ensures that if another libc is used, symlinks are present such that the
compiler can be found. The base version is always assumed to be "glibc"
with symlinks from musl and uclibc compiler names.

This means gcc-cross-canadian is consistent regardless of which libc is
selected when its build in multimachine builds.

[YOCTO #8025]

(From OE-Core rev: 83ead626c0da75edec2833ffb1a29011ec7b83d2)

Signed-off-by: Richard Purdie

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