**** BEGIN LOGGING AT Fri Apr 19 02:59:57 2019
Apr 19 15:02:51 <bluca> hi, question about the sdk build: when building the sdk for a sumo-based distro, I have a nativesdk recipe that uses ${SDK_ARCH}, but the resulting file is getting the host arch rather than the target arch
Apr 19 15:03:08 <bluca> ie: x86_64 rather than aarch64
Apr 19 15:03:20 <bluca> what should I use in the bb file instead of SDK_ARCH to get the target?
Apr 19 15:15:21 <kergoth> SDK_ARCH is hte arch the sdk will be installed on. the host the sdk is targeting.
Apr 19 15:15:27 <kergoth> not the machine it's built for
Apr 19 15:15:45 <kergoth> TARGET_ARCH corresponds to MACHINE, SDK_ARCH corresponds to SDKMACHINE
Apr 19 15:25:11 <bluca> ok - then shouldn't the nativesdk-meson file produce a meson.cross using TARGET_ARCH rather than SDK_ARCH?
Apr 19 15:25:11 <bluca> https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-devtools/meson/nativesdk-meson_0.50.0.bb
Apr 19 15:27:08 <kergoth> no
Apr 19 15:27:26 <kergoth> nativesdk == the sdk version of native. binaries targeting the host the sdk will run on
Apr 19 15:27:48 <kergoth> regular target recipes are installed into the sdk with TOOLCHAIN_HOST_TASK, those target TARGET_ARCH
Apr 19 15:28:01 <kergoth> and cross-canadian recipes run on SDK_ARCH but target TARGET_ARCH, i.e. shipping a toolchain in the sdk
Apr 19 15:28:30 <bluca> I see, thank
Apr 19 15:28:32 <bluca> s
Apr 19 15:28:41 <kergoth> crosssdk = the recipes building on BUILD_ARCH but targeting SDK_ARCH, i.e. it builds the toolchain to target SDK_ARCH, which is important if SDK_ARCH != BUILD_ARCH. i.e. you could build on an i386 host but build an sdk to run on x86_64
Apr 19 15:28:52 <kergoth> and cross runs on BUILD_ARCH but targets TARGET_ARCH
Apr 19 15:28:56 <kergoth> that sums up most of the recipe variants
Apr 19 15:36:18 <bluca> I guess my confusion stemmed from the fact that the meson.cross files I'm used to see are used for cross compilation and thus have the host definitions, eg: https://github.com/DPDK/dpdk/blob/master/config/arm/arm64_armv8_linux_gcc#L10
Apr 19 15:37:15 <bluca> while the one generated by that recipe has the build arch filled in, despite the tooling pointing to the aarch64 toolchain
Apr 19 15:37:57 <kergoth> most likely our meson.bbclass controls telling it to use our toolchain, rather than patching it to do so, but even if it did, that'd be a cross or cross-canadian recipe, not native/nativesdk
Apr 19 15:38:00 <kergoth> hopefully that clarifies
Apr 19 15:38:09 <kergoth> but yeah, there's a lot going on, it's easy to get confused :)
Apr 19 15:40:08 <bluca> yep :-) thanks again for the pointers
**** ENDING LOGGING AT Sat Apr 20 02:59:56 2019