| Summary: |
SDKPATH should not reference SDK_VERSION |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Yann Dirson <ydirson> |
| Component: |
oe-core other | Assignee: |
Richard Purdie <richard.purdie> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium+
|
CC: |
randy.macleod, richard.purdie
|
| Version: |
unspecified | |
|
| Target Milestone: |
3.4 M3 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
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.