| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
|
|
|
| |
We want to avoid modifying the default package, as it can break Yocto
Project Compatibility guidelines.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
|
|
|
| |
These items are specific to the special PetaLinux/Vitis multilib toolchain,
move these to meta-petalinux.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
| |
This is the result of automated script (0.9.0) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
| |
Multiple copies of the same binary toolchain will not help with anything,
so limit use to a single (primary) lib toolchain, and then new symlinks
to those toolchains to continue to enable the environment files.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
Distro Changes:
When building a multilib, we need to disable configsite cache. Otherwise
the system will fail to generate the SDK as there are no configsite entries
due to newlib based multilibs.
Recipe Changes:
gcc - globally disable multilib configuration
- Disable Linux specific configurations (EXTRACONFFUNCS)
gcc-cross-canadian - enable multilib on a recipe specific basis
libgcc - add a noop override to do_multilib_install to avoid Linux specific
multilib processing
newlib - arm/v6+m/nofp and arm/v8-m.base/nofp do not have newlib trap
implementations. libgloss contains these, workaround by
disabling builtin trap syscall handler.
- misc workarounds for multilib installs
libgloss - Allow MLPREFIX for newlib dependencies
meta-toolchain - adjust to install only the items we want/need
packagegroup-newlib-standalone-sdk-target - new pkggroup for the
custom baremetal SDK to select the right set of packages
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
