Skip to contentSkip to conversation

nativesdk-cmake can't use a separate build dir, currently fails to build

PATCH Jonathan Austin 1 participant 1 message May 9, 2014

lore
Share & tools
lore
#0 lore raw

Hi all,

I've discovered today that nativesdk-cmake fails to build by default. The cmake and cmake-native targets still work.

The difference appears to be the metadata in:

meta/conf/distro/include/seperatebuilddir.inc

...which tells bitbake not to use a separate build dir for the latter two targets, but doesn't make the exception for nativesdk-cmake

I got things working again with the following hack:

---8<-------

meta/conf/distro/include/seperatebuilddir.inc +1 -1
index 8f2ebfa..2ece812 100644
@@ -473,7 +473,7 @@ B_pn-nativesdk-bigreqsproto = "${SEPB}"
 B_pn-nativesdk-bison = "${SEPB}"
 B_pn-nativesdk-bzip2 = "${SEPB}"
 B_pn-nativesdk-chrpath = "${SEPB}"
-B_pn-nativesdk-cmake = "${SEPB}"
+#B_pn-nativesdk-cmake = "${SEPB}"
 B_pn-nativesdk-curl = "${SEPB}"
 B_pn-nativesdk-db = "${SEPB}"
 B_pn-nativesdk-dbus = "${SEPB}"

----->8-------

I'm not really sure what the 'right' way to remove this is - the two existing cmake targets are just commented out, but recent patches seem to be simply removing targets.

Is this the appropriate fix? Does anyone know if there's a reason for two out of three cmake targets to be commented but not the third? Did it work once?

Any guidance one what the actual patch should look like is welcome!

Jonny