summaryrefslogtreecommitdiff
path: root/meta/classes/crosssdk.bbclass
diff options
context:
space:
mode:
authorIlya Yanok <yanok@emcraft.com>2011-04-05 03:13:45 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-04-05 17:13:45 +0100
commit0d4ea5d7486dc35001582bef3ff6ebfad0606bda (patch)
treef42d4686e67d4fb907b19c7c06eb7fada921c664 /meta/classes/crosssdk.bbclass
parent694db055f3729662e0e0193a31f2098be599877f (diff)
downloadopenembedded-core-0d4ea5d7486dc35001582bef3ff6ebfad0606bda.tar.gz
openembedded-core-0d4ea5d7486dc35001582bef3ff6ebfad0606bda.tar.bz2
openembedded-core-0d4ea5d7486dc35001582bef3ff6ebfad0606bda.zip
native, nativesdk, crosssdk: reset TARGET_FPU
When building one of the native, nativesdk or crosssdk packages TARGET_* variables' values are no longer related to the target we set via MACHINE variable, they are now related to the BUILD (native) or SDK (nativesdk, crosssdk) targets instead. We need to change TARGET_FPU variable accordingly or some of the recipes (the ones that check for TARGET_FPU value, most notably gcc and eglibc) might be confused. It's probably cleaner not to reset TARGET_FPU but to change it to something like ${BUILD_FPU} (for native) or ${SDK_FPU} (for crosssdk and nativesdk) but as long as BUILD and SDK are x86 it's safe to just reset TARGET_FPU. Signed-off-by: Ilya Yanok <yanok@emcraft.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/crosssdk.bbclass')
-rw-r--r--meta/classes/crosssdk.bbclass1
1 files changed, 1 insertions, 0 deletions
diff --git a/meta/classes/crosssdk.bbclass b/meta/classes/crosssdk.bbclass
index 75fcfefc09..3952ebdca4 100644
--- a/meta/classes/crosssdk.bbclass
+++ b/meta/classes/crosssdk.bbclass
@@ -9,6 +9,7 @@ TARGET_VENDOR = "${SDK_VENDOR}"
TARGET_OS = "${SDK_OS}"
TARGET_PREFIX = "${SDK_PREFIX}"
TARGET_CC_ARCH = "${SDK_CC_ARCH}"
+TARGET_FPU = ""
target_libdir = "${SDKPATHNATIVE}${libdir_nativesdk}"
target_includedir = "${SDKPATHNATIVE}${includedir_nativesdk}"