Bug 14100 - SDKPATH should not reference SDK_VERSION
Summary: SDKPATH should not reference SDK_VERSION
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: oe-core other (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 3.4 M3
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-10-20 07:16 UTC by Yann Dirson
Modified: 2021-08-02 14:54 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yann Dirson 2020-10-20 07:16:09 UTC 
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.
Comment 1 Richard Purdie 2020-10-22 08:01:36 UTC 
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?