| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The key is using COMPATIBLE_HOST to declare, for each recipe, which
OS they are compatible with. This is a regex, so we need to
carefully specify the arch/vendor wild cardscomponents so that we match
only the OS parts.
In the distro configuration, default to the standard Linux HOST_SYS
setting.
In the various baremetal recipes (or esw class) set the specific
compatibility to allow baremetal recipes to build.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
compatibility"
This reverts commit 4f3edb6da405ffff957d6f194bc7db7bdd9f1463.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Following the example of base.bbclass in OE-Core, a new COMPATIBLE_OS
variable is defined. Similar to COMPATIBLE_MACHINE, it is a regex that
can be used to declare TARGET_OS string compatibility on a per-recipe
basis. Either the distro configuration or the recipes themselves will
need to inherit this class.
By default the class assumes we're building a Linux based system, and
thus any recipe who has not declared compatibility is compatible with
Linux. The default compatible field was copied from bitbake.conf to
ensure there are no surprised.
Additionally, enable the usage of this class throughout
meta-xilinx-standalone layer.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|