| Summary: |
Support for self-contained "baremetal" CPU meta-layers |
| Product: |
[Build System, Metadata & Runtime] BitBake
|
Reporter: |
Juro Bystricky <juro.bystricky> |
| Component: |
bitbake | Assignee: |
Richard Purdie <richard.purdie> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
Daniel Istrate <daniel.alexandrux.istrate> |
| Severity: |
enhancement
|
|
|
| Priority: |
Medium
|
CC: |
alexandru.c.georgescu, poky.bs.watcher, poky.watcher, tim.orling
|
| Version: |
2.1 | |
|
| Target Milestone: |
2.2 M3 | |
|
| Hardware: |
All | |
|
| OS: |
other | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|
Verified:
|
|
Documentation change:
|
Yes (doc changes required)
|
Support already exists for building "baremetal" cross-compilers for various CPUs. At present, when adding a new CPU support, we need to modify time: meta/classes/insane.bbclass meta/classes/kernel-arch.bbclass meta/classes/siteinfo.bbclass The modifications themselves are simple, but it would be a cleaner solution if whatever info is needed by these classes would be pulled from CPU specific meta-layer (somehow). This way the meta-layer would be self-contained.