Bug 8554 - Support for self-contained "baremetal" CPU meta-layers
Summary: Support for self-contained "baremetal" CPU meta-layers
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.1
Hardware: All other
: Medium enhancement
Target Milestone: 2.2 M3
Assignee: Richard Purdie
QA Contact: Daniel Istrate
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-10-22 00:43 UTC by Juro Bystricky
Modified: 2016-07-26 13:57 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

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 Juro Bystricky 2015-10-22 00:43:16 UTC 
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.
Comment 1 Juro Bystricky 2015-10-22 00:44:16 UTC 
s/we need to modify time:/we need to modify:/
Comment 2 Richard Purdie 2016-07-22 14:28:58 UTC 
I've posted patches for siteinfo and insane. For kernel-arch, firstly there are only a limited number of supported linux kernel arches and secondly, an overide like ARCH_pn-linux-XXX = "Y" can usually be used. I'm therefore not proposing to change that one.