| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1065455
Microblaze does not support initfini_array in a baremetal configuration.
This has previously been disabled in binutils, but it was missed in GCC and
related libraries.
This patch slightly restructures the baremetal configurations to move the
common configuration elements into a single configure set. This matches the
behavior from the Yocto Project gcc-configure-common.inc file.
Signed-off-by: Mark Hatle <mark.hatle@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>
|
| |
|
|
|
|
|
|
|
| |
When appending file paths the ':' should be at the beginning of the
path. The patched appending lines were still working because there was
no paths added after the '__default:'
Fixing typo to ensure no breakages later
Signed-off-by: Jaewon Lee <jaewon.lee@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>
|
| |
|
|
|
|
|
|
| |
When the xilinx-standalone distribution is not enabled, we need to make sure
that we do not affect various task hashes. This conforms to the Yocto
Project Compliance requirements.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enable the following multilibs:
.
le
bs
p
m
fpd
m/fpd
p/m
p/fpd
p/m/fpd
bs/p
bs/m
bs/fpd
bs/m/fpd
bs/p/m
bs/p/fpd
bs/p/m/fpd
le/m64
le/bs
le/p
le/m
le/fpd
le/m/fpd
le/p/m
le/p/fpd
le/p/m/fpd
le/bs/p
le/bs/m
le/bs/fpd
le/bs/m/fpd
le/bs/p/m
le/bs/p/fpd
le/bs/p/m/fpd
le/m64/bs
le/m64/p
le/m64/m
le/m64/fpd
le/m64/m/fpd
le/m64/p/m
le/m64/p/fpd
le/m64/p/m/fpd
le/m64/bs/p
le/m64/bs/m
le/m64/bs/fpd
le/m64/bs/m/fpd
le/m64/bs/p/m
le/m64/bs/p/fpd
le/m64/bs/p/m/fpd
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
As part of the merge of the code bases, changes were introduced that
changed the way the cortexr5 was defined. To sync this between the
baremetal compilation and the baremetal toolchain compilation we
create a new armrm tune file, define a new tune feature of 'armrm',
define 'armrm' as a new machine override based on the feature 'armrm',
and move the cortexr5 tuning to a common file.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
| |
The C++ headers are slightly different for different multilibs. The Yocto
Project name (canonical arch) is different then the gcc multilib directory
name. Put in code that will syncronize these two items, allows C++ support
to function properly, avoiding conflicts in the process.
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>
|
| |
|
|
|
|
| |
zynqmp and versal variants
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
| |
|
|
| |
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
|
on recipes-devtools
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
