| Summary: |
SDKMACHINE can't be set in the distro config |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Paul Eggleton <bluelightning> |
| Component: |
core | Assignee: |
Paul Eggleton <bluelightning> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
meta.mr.watcher, meta.watcher, sgw, srifenbark
|
| Version: |
1.5.1 | |
|
| Target Milestone: |
1.6 | |
|
| Hardware: |
All | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
02 April 2014: Doc flag set to "Done." |
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|
Verified:
|
|
Documentation change:
|
Done (doc changes complete)
|
If you set SDKMACHINE in the distro config it will not have any effect; this is because of the ordering in meta/conf/bitbake.conf: ... include conf/machine-sdk/${SDKMACHINE}.conf include conf/distro/${DISTRO}.conf ... The value won't get set until after the line where its value would have any effect has been parsed. Assuming we can't reorder the includes in bitbake.conf, I think we should add a check in sanity.bbclass to see if the include actually happened assuming SDKMACHINE has a value. This should be a simple matter of checking BBINCLUDED.