d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
releases
numam-dpdk/config/arm/arm64_armv8_linux_gcc

18 lines
408 B
Plaintext
Raw Permalink Normal View History

build: support vendor specific ARM cross builds Add various vendor specific cross build targets. This can be verified by using linaro toolchain and running meson build --cross-file config/arm/arm64_<cpu>_<platform>_<compiler> In future more cross build targets can be added. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-01-22 15:26:31 +00:00
[binaries]
build: add ccache for cross compilation By default, ccache is not used for cross build[1]. Update all cross files to use ccache if it is available in build machine. Also, updated devtools/test-meson-builds.sh script to find the correct DPDK_TARGET due to change in cross file syntax. [1] https://mesonbuild.com/Machine-files.html Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Stanislaw Kardach <kda@semihalf.com> Acked-by: Chengwen Feng <fengchengwen@huawei.com> Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
2022-06-08 17:13:04 +00:00
c = ['ccache', 'aarch64-linux-gnu-gcc']
config: fix C++ cross compiler for Arm and PPC Through some mixup all cross-files for ARM and PowerPC platforms were using C Preprocessor (cpp) instead of GCC (g++). This caused meson to fail detecting the C++ compiler presence and therefore disabling some targets (i.e. C++ include file checks). Fixes: e53a5299d219 ("build: support vendor specific ARM cross builds") Cc: stable@dpdk.org Signed-off-by: Stanislaw Kardach <kda@semihalf.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2022-06-21 12:28:23 +00:00
cpp = ['ccache', 'aarch64-linux-gnu-g++']
build: support vendor specific ARM cross builds Add various vendor specific cross build targets. This can be verified by using linaro toolchain and running meson build --cross-file config/arm/arm64_<cpu>_<platform>_<compiler> In future more cross build targets can be added. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-01-22 15:26:31 +00:00
ar = 'aarch64-linux-gnu-gcc-ar'
build: add more implementers IDs and PNs for ARM 1) Add native PN option '-march=native' to allow automatic detection. Set 'arm_force_native_march' to 'true' in config/arm/meson.build to use native PN option. 2) Add implementer_pn option for part num selection in cross compile 3) Add known Arm cortex PN support 4) Add known implementers' IDs (use generic flags/archs by default) 5) Sync build options with config/common_armv8a_linuxapp Signed-off-by: Herbert Guan <herbert.guan@arm.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2018-01-31 07:39:19 +00:00
strip = 'aarch64-linux-gnu-strip'
config: add pkgconfig for arm64 Meson fails to find a pkg-config executable if pkgconfig isn't set for aarch64. The environment variable `PKG_CONFIG_PATH` is useless in this case, and meson fails to locate dependencies that are built in non-standard paths. Signed-off-by: Ali Alnubani <alialnu@mellanox.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-11-28 07:24:38 +00:00
pkgconfig = 'aarch64-linux-gnu-pkg-config'
build: improve pcap dependency handling pcap has historically shipped a custom pcap-config binary tool which does the job of pkg-config. It was never compatible with cross compilation. Meson uses it when using dependency(), which then means cross compilation fails. Set pcap-config to empty in the meson cross compilation files so that Meson will not use it, and add a fallback in case dependency() fails. libpcap 1.9.0 finally ships a pkg-config file so everything will work out of the box in the future. Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
2019-02-26 17:46:37 +00:00
pcap-config = ''
build: support vendor specific ARM cross builds Add various vendor specific cross build targets. This can be verified by using linaro toolchain and running meson build --cross-file config/arm/arm64_<cpu>_<platform>_<compiler> In future more cross build targets can be added. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-01-22 15:26:31 +00:00
[host_machine]
system = 'linux'
cpu_family = 'aarch64'
cpu = 'armv8-a'
endian = 'little'
build: add more implementers IDs and PNs for ARM 1) Add native PN option '-march=native' to allow automatic detection. Set 'arm_force_native_march' to 'true' in config/arm/meson.build to use native PN option. 2) Add implementer_pn option for part num selection in cross compile 3) Add known Arm cortex PN support 4) Add known implementers' IDs (use generic flags/archs by default) 5) Sync build options with config/common_armv8a_linuxapp Signed-off-by: Herbert Guan <herbert.guan@arm.com> Acked-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
2018-01-31 07:39:19 +00:00
[properties]
config/arm: reformat and move config and comments Change formatting so that it's more consistent and readable, add/modify comments/stdout messages, move configuration options to more appropriate places and make the order consistent according to these rules: 1. First list generic configuration options, then list options that may be overwritten. List SoC-specific options last. 2. For SoC-specific options, list number of cores before the number of NUMA nodes, to make it consistent with config/meson.build. Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Jerin Jacob <jerinj@marvell.com> Tested-by: Jerin Jacob <jerinj@marvell.com> Tested-by: Pavan Nikhilesh <pbhagavatula@marvell.com> Tested-by: Vimal Chungath <vcchunga@amazon.com> Tested-by: Dharmik Thakkar <dharmik.thakkar@arm.com>
2021-01-15 13:26:01 +00:00
# Generate binaries that are portable across all Armv8 machines
config/arm: add platform config option Add Arm SoC configuration sets to Arm meson.build and add an arch agnostic meson option, 'platform', to select from these SoC configurations for meson native builds. This is preferable to specifying a cross file when doing aarch64 -> aarch64 builds, since the cross file specifies the toolchain as well. Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com> Tested-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
2021-04-14 13:41:35 +00:00
platform = 'generic'
Reference in New Issue Copy Permalink