summaryrefslogtreecommitdiffstats
path: root/meta/classes/package.bbclass
diff options
context:
space:
mode:
authorPeter Seebach <peter.seebach@windriver.com>2012-07-27 16:54:48 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-07-29 10:16:16 +0100
commit3d164f74fdb994c08c7e3f6d93cd4e1959b4eb7e (patch)
treeddfacf53d687f9b9df776e09ebade0970311d1c6 /meta/classes/package.bbclass
parenta18b397a3ea101083ff8249f7f0ac16e1b2e9a2c (diff)
downloadast2050-yocto-poky-3d164f74fdb994c08c7e3f6d93cd4e1959b4eb7e.zip
ast2050-yocto-poky-3d164f74fdb994c08c7e3f6d93cd4e1959b4eb7e.tar.gz
pseudo.inc/pseudo_1.4.bb: update pseudo to 1.4
This update replaces the half-baked --arch logic with the use of $CFLAGS to pick compiler flags, on the grounds that it makes a lot more sense for the build system to pick flags than for pseudo to try to guess what they should be; this should allow pseudo to at least compile for targets, and possibly run on them. This doesn't solve the problem of guessing how to forcibly build the 32-bit variant on hosts, because we really don't have a general solution for that. There's no idiom for "given this set of compiler flags and this architecture, what flags would you use to request a 32-bit compile instead?" So we basically ignore that for now. If someone comes along trying to use the build system to build pseudo-native on a 64-bit host that also supports 32-bit binaries and isn't x86, we will revisit this. (From OE-Core rev: 711fcb4f10e2cefd7ff6e1921d87d1cad840d0c8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/package.bbclass')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud