14100 2020-10-20 07:16:09 +0000 SDKPATH should not reference SDK_VERSION 2021-08-02 14:54:17 +0000 1 1 7 Build System, Metadata & Runtime OE-Core oe-core other unspecified x86 Multiple RESOLVED FIXED Medium+ normal 3.4 M3 1 ydirson richard.purdie randy.macleod richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 88438 0 ydirson 2020-10-20 07:16:09 +0000 crosssdk.bbclass sets eg. this: target_libdir = "${SDKPATHNATIVE}${libdir_nativesdk}" This causes all crosssdk recipes (starting with binutils-crosssdk) to see their hash change on any DISTRO_VERSION change (be it as minor as a bugfix dot-release). OTOH, hardcoding this version in packages targetting the SDK does not seem to make sense, as the SDK itself is fully relocatable. It sounds like we only need the current SDKPATH value as a default path for the sdk relocation step. At first glance it even looks like the ${DISTRO} part of SDKPATH can also be removed too, as it looks like the only typical reference to it is in conf/distro/ itself, and could help to share sstate between poky and downstream distros. 88460 1 richard.purdie 2020-10-22 08:01:36 +0000 I think this is a valid concern. The SDK is relocatable now so we could use a "bland" path and then just use the default install path for the SDK to possibly contain distro and version? 91082 2 richard.purdie 2021-08-02 14:54:17 +0000 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=f62f684de861bddc225cee66f33781d328a20f95 http://git.yoctoproject.org/cgit.cgi/meta-yocto/commit/?id=a62175ee581bd05661717f0fb89dad2a297b4034