2017-12-18 15:56:25 +00:00
|
|
|
# SPDX-License-Identifier: BSD-3-Clause
|
2019-04-02 03:54:49 +00:00
|
|
|
# Copyright(c) 2017-2019 Intel Corporation
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
|
2019-04-09 10:55:35 +00:00
|
|
|
# check the OS is supported, rather than going any further
|
|
|
|
supported_exec_envs = ['freebsd', 'linux', 'windows']
|
|
|
|
exec_env = host_machine.system()
|
|
|
|
if not supported_exec_envs.contains(exec_env)
|
2021-04-20 10:22:23 +00:00
|
|
|
error('unsupported system type "@0@"'.format(exec_env))
|
2019-04-09 10:55:35 +00:00
|
|
|
endif
|
|
|
|
|
2019-04-09 10:55:36 +00:00
|
|
|
# define a handy variable for checking which OS we have.
|
|
|
|
# gives us "is_windows", "is_freebsd" and "is_linux"
|
|
|
|
foreach env:supported_exec_envs
|
2021-04-20 10:22:23 +00:00
|
|
|
set_variable('is_' + env, exec_env == env)
|
2019-04-09 10:55:36 +00:00
|
|
|
endforeach
|
|
|
|
|
2020-02-27 04:25:34 +00:00
|
|
|
# MS linker requires special treatment.
|
|
|
|
# TODO: use cc.get_linker_id() with Meson >= 0.54
|
|
|
|
is_ms_linker = is_windows and (cc.get_id() == 'clang')
|
|
|
|
|
2019-03-15 18:20:20 +00:00
|
|
|
# set the major version, which might be used by drivers and libraries
|
|
|
|
# depending on the configuration options
|
|
|
|
pver = meson.project_version().split('.')
|
|
|
|
major_version = '@0@.@1@'.format(pver.get(0), pver.get(1))
|
2021-04-20 10:22:23 +00:00
|
|
|
abi_version = run_command(find_program('cat', 'more'), abi_version_file).stdout().strip()
|
2019-12-12 11:58:26 +00:00
|
|
|
|
2020-06-26 08:16:36 +00:00
|
|
|
# Libraries have the abi_version as the filename extension
|
2019-12-12 11:58:26 +00:00
|
|
|
# and have the soname be all but the final part of the abi_version.
|
2020-06-26 08:16:36 +00:00
|
|
|
# e.g. v20.1 => librte_foo.so.20.1
|
|
|
|
# sonames => librte_foo.so.20
|
2020-08-10 15:10:20 +00:00
|
|
|
so_version = abi_version.split('.')[0]
|
2019-03-15 18:20:20 +00:00
|
|
|
|
2019-03-15 18:20:21 +00:00
|
|
|
# extract all version information into the build configuration
|
|
|
|
dpdk_conf.set('RTE_VER_YEAR', pver.get(0).to_int())
|
|
|
|
dpdk_conf.set('RTE_VER_MONTH', pver.get(1).to_int())
|
|
|
|
if pver.get(2).contains('-rc')
|
2021-04-20 10:22:23 +00:00
|
|
|
rc_ver = pver.get(2).split('-rc')
|
|
|
|
dpdk_conf.set('RTE_VER_MINOR', rc_ver.get(0).to_int())
|
|
|
|
dpdk_conf.set_quoted('RTE_VER_SUFFIX', '-rc')
|
|
|
|
dpdk_conf.set('RTE_VER_RELEASE', rc_ver.get(1).to_int())
|
2019-03-15 18:20:21 +00:00
|
|
|
else
|
2021-04-20 10:22:23 +00:00
|
|
|
dpdk_conf.set('RTE_VER_MINOR', pver.get(2).to_int())
|
|
|
|
dpdk_conf.set_quoted('RTE_VER_SUFFIX', '')
|
2019-03-15 18:20:21 +00:00
|
|
|
# for actual, non-rc releases, set the release value to 99 to ensure releases
|
|
|
|
# have higher version numbers than their respective release candidates
|
2021-04-20 10:22:23 +00:00
|
|
|
dpdk_conf.set('RTE_VER_RELEASE', 99)
|
2019-03-15 18:20:21 +00:00
|
|
|
endif
|
|
|
|
|
2019-03-15 18:20:20 +00:00
|
|
|
pmd_subdir_opt = get_option('drivers_install_subdir')
|
|
|
|
if pmd_subdir_opt.contains('<VERSION>')
|
2021-04-20 10:22:23 +00:00
|
|
|
pmd_subdir_opt = abi_version.join(pmd_subdir_opt.split('<VERSION>'))
|
2019-03-15 18:20:20 +00:00
|
|
|
endif
|
|
|
|
driver_install_path = join_paths(get_option('libdir'), pmd_subdir_opt)
|
|
|
|
eal_pmd_path = join_paths(get_option('prefix'), driver_install_path)
|
|
|
|
|
2019-05-02 16:51:53 +00:00
|
|
|
# driver .so files often depend upon the bus drivers for their connect bus,
|
|
|
|
# e.g. ixgbe depends on librte_bus_pci. This means that the bus drivers need
|
|
|
|
# to be in the library path, so symlink the drivers from the main lib directory.
|
2020-10-31 06:56:50 +00:00
|
|
|
if not is_windows
|
2021-04-20 10:22:23 +00:00
|
|
|
meson.add_install_script('../buildtools/symlink-drivers-solibs.sh',
|
|
|
|
get_option('libdir'), pmd_subdir_opt)
|
2020-10-31 06:56:50 +00:00
|
|
|
endif
|
2019-05-02 16:51:53 +00:00
|
|
|
|
2021-04-14 13:41:34 +00:00
|
|
|
# init disable/enable driver lists that will be populated in different places
|
|
|
|
disable_drivers = ''
|
|
|
|
enable_drivers = ''
|
|
|
|
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
# set the machine type and cflags for it
|
2017-12-15 17:12:43 +00:00
|
|
|
if meson.is_cross_build()
|
2021-04-20 10:22:23 +00:00
|
|
|
machine = host_machine.cpu()
|
2017-12-15 17:12:43 +00:00
|
|
|
else
|
2021-04-20 10:22:23 +00:00
|
|
|
machine = get_option('machine')
|
2017-12-15 17:12:43 +00:00
|
|
|
endif
|
2018-11-14 19:40:12 +00:00
|
|
|
|
2021-03-30 06:40:19 +00:00
|
|
|
# machine type 'generic' is special, it selects the per arch agreed common
|
|
|
|
# minimal baseline needed for DPDK. Machine type 'default' is also supported
|
|
|
|
# with the same meaning for backwards compatibility.
|
2018-11-14 19:40:12 +00:00
|
|
|
# That might not be the most optimized, but the most portable version while
|
|
|
|
# still being able to support the CPU features required for DPDK.
|
|
|
|
# This can be bumped up by the DPDK project, but it can never be an
|
|
|
|
# invariant like 'native'
|
2021-03-30 06:40:19 +00:00
|
|
|
if machine == 'default' or machine == 'generic'
|
2021-04-20 10:22:23 +00:00
|
|
|
if host_machine.cpu_family().startswith('x86')
|
|
|
|
# matches the old pre-meson build systems generic machine
|
|
|
|
machine = 'corei7'
|
|
|
|
elif host_machine.cpu_family().startswith('arm')
|
|
|
|
machine = 'armv7-a'
|
|
|
|
elif host_machine.cpu_family().startswith('aarch')
|
|
|
|
# arm64 manages generic config in config/arm/meson.build
|
|
|
|
machine = 'generic'
|
|
|
|
elif host_machine.cpu_family().startswith('ppc')
|
|
|
|
machine = 'power8'
|
|
|
|
endif
|
2018-11-14 19:40:12 +00:00
|
|
|
endif
|
|
|
|
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
dpdk_conf.set('RTE_MACHINE', machine)
|
2018-01-22 15:26:30 +00:00
|
|
|
machine_args = []
|
2018-11-14 19:40:11 +00:00
|
|
|
|
|
|
|
# ppc64 does not support -march= at all, use -mcpu and -mtune for that
|
|
|
|
if host_machine.cpu_family().startswith('ppc')
|
2021-04-20 10:22:23 +00:00
|
|
|
machine_args += '-mcpu=' + machine
|
|
|
|
machine_args += '-mtune=' + machine
|
2018-09-10 11:32:43 +00:00
|
|
|
else
|
2021-04-20 10:22:23 +00:00
|
|
|
machine_args += '-march=' + machine
|
2018-09-10 11:32:43 +00:00
|
|
|
endif
|
build: remove library special cases
The EAL and compat libraries were special-cases in the library build
process, the former because of it's complexity, and the latter because
it only consists of a single header file.
By reworking the EAL meson.build files, we can eliminate the need for it to
be a special case, by having it build up and return the list of sources,
headers, and objects and return those to the higher level build file. This
should also simplify the building of EAL, as we can eliminate a number of
meson.build files that would no longer be needed, and have fewer, but
larger meson.build files (9 now vs 14 previous) - thereby making the logic
easier to follow and items easier to find.
Once done, we can pull eal into the main library loop, with some
modifications to support it. Compat can also be pulled it once we add in a
check to handle the case of an empty sources list.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Luca Boccassi <bluca@debian.org>
2017-11-03 14:47:43 +00:00
|
|
|
|
2018-04-03 11:24:52 +00:00
|
|
|
toolchain = cc.get_id()
|
|
|
|
dpdk_conf.set_quoted('RTE_TOOLCHAIN', toolchain)
|
|
|
|
dpdk_conf.set('RTE_TOOLCHAIN_' + toolchain.to_upper(), 1)
|
|
|
|
|
2018-09-26 09:15:36 +00:00
|
|
|
dpdk_conf.set('RTE_ARCH_64', cc.sizeof('void *') == 8)
|
2020-09-11 15:39:59 +00:00
|
|
|
dpdk_conf.set('RTE_ARCH_32', cc.sizeof('void *') == 4)
|
2018-09-26 09:15:36 +00:00
|
|
|
|
2020-02-27 04:25:37 +00:00
|
|
|
if not is_windows
|
2021-04-20 10:22:23 +00:00
|
|
|
add_project_link_arguments('-Wl,--no-as-needed', language: 'c')
|
2020-02-27 04:25:37 +00:00
|
|
|
endif
|
2018-10-27 09:17:50 +00:00
|
|
|
|
2020-02-27 04:25:37 +00:00
|
|
|
# use pthreads if available for the platform
|
2020-06-20 22:35:42 +00:00
|
|
|
if not is_windows
|
2021-04-20 10:22:23 +00:00
|
|
|
add_project_link_arguments('-pthread', language: 'c')
|
|
|
|
dpdk_extra_ldflags += '-pthread'
|
2020-02-27 04:25:37 +00:00
|
|
|
endif
|
build: remove library special cases
The EAL and compat libraries were special-cases in the library build
process, the former because of it's complexity, and the latter because
it only consists of a single header file.
By reworking the EAL meson.build files, we can eliminate the need for it to
be a special case, by having it build up and return the list of sources,
headers, and objects and return those to the higher level build file. This
should also simplify the building of EAL, as we can eliminate a number of
meson.build files that would no longer be needed, and have fewer, but
larger meson.build files (9 now vs 14 previous) - thereby making the logic
easier to follow and items easier to find.
Once done, we can pull eal into the main library loop, with some
modifications to support it. Compat can also be pulled it once we add in a
check to handle the case of an empty sources list.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Luca Boccassi <bluca@debian.org>
2017-11-03 14:47:43 +00:00
|
|
|
|
2019-04-02 03:54:49 +00:00
|
|
|
# on some OS, maths functions are in a separate library
|
2020-01-09 12:59:15 +00:00
|
|
|
if cc.find_library('m', required : false).found()
|
2021-04-20 10:22:23 +00:00
|
|
|
# some libs depend on maths lib
|
|
|
|
add_project_link_arguments('-lm', language: 'c')
|
|
|
|
dpdk_extra_ldflags += '-lm'
|
2019-04-02 03:54:49 +00:00
|
|
|
endif
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
|
2019-04-09 10:55:36 +00:00
|
|
|
if is_linux
|
2021-04-20 10:22:23 +00:00
|
|
|
link_lib = 'dl'
|
2019-04-02 03:54:49 +00:00
|
|
|
else
|
2021-04-20 10:22:23 +00:00
|
|
|
link_lib = ''
|
2019-04-02 03:54:49 +00:00
|
|
|
endif
|
|
|
|
|
|
|
|
# if link_lib is empty, do not add it to project properties
|
|
|
|
if link_lib != ''
|
2021-04-20 10:22:23 +00:00
|
|
|
add_project_link_arguments('-l' + link_lib, language: 'c')
|
|
|
|
dpdk_extra_ldflags += '-l' + link_lib
|
build: remove library special cases
The EAL and compat libraries were special-cases in the library build
process, the former because of it's complexity, and the latter because
it only consists of a single header file.
By reworking the EAL meson.build files, we can eliminate the need for it to
be a special case, by having it build up and return the list of sources,
headers, and objects and return those to the higher level build file. This
should also simplify the building of EAL, as we can eliminate a number of
meson.build files that would no longer be needed, and have fewer, but
larger meson.build files (9 now vs 14 previous) - thereby making the logic
easier to follow and items easier to find.
Once done, we can pull eal into the main library loop, with some
modifications to support it. Compat can also be pulled it once we add in a
check to handle the case of an empty sources list.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Luca Boccassi <bluca@debian.org>
2017-11-03 14:47:43 +00:00
|
|
|
endif
|
|
|
|
|
2017-10-12 14:02:27 +00:00
|
|
|
# check for libraries used in multiple places in DPDK
|
|
|
|
has_libnuma = 0
|
2021-01-15 13:26:08 +00:00
|
|
|
find_libnuma = true
|
|
|
|
if meson.is_cross_build() and not meson.get_cross_property('numa', true)
|
2021-04-20 10:22:23 +00:00
|
|
|
# don't look for libnuma if explicitly disabled in cross build
|
|
|
|
find_libnuma = false
|
2021-01-15 13:26:08 +00:00
|
|
|
endif
|
|
|
|
if find_libnuma
|
2021-04-20 10:22:23 +00:00
|
|
|
numa_dep = cc.find_library('numa', required: false)
|
|
|
|
if numa_dep.found() and cc.has_header('numaif.h')
|
|
|
|
dpdk_conf.set10('RTE_HAS_LIBNUMA', true)
|
|
|
|
has_libnuma = 1
|
|
|
|
add_project_link_arguments('-lnuma', language: 'c')
|
|
|
|
dpdk_extra_ldflags += '-lnuma'
|
|
|
|
endif
|
2017-10-12 14:02:27 +00:00
|
|
|
endif
|
|
|
|
|
2020-09-02 11:10:30 +00:00
|
|
|
has_libfdt = 0
|
|
|
|
fdt_dep = cc.find_library('libfdt', required: false)
|
|
|
|
if fdt_dep.found() and cc.has_header('fdt.h')
|
2021-04-20 10:22:23 +00:00
|
|
|
dpdk_conf.set10('RTE_HAS_LIBFDT', true)
|
|
|
|
has_libfdt = 1
|
|
|
|
add_project_link_arguments('-lfdt', language: 'c')
|
|
|
|
dpdk_extra_ldflags += '-lfdt'
|
2020-09-02 11:10:30 +00:00
|
|
|
endif
|
|
|
|
|
2021-02-25 01:49:19 +00:00
|
|
|
libexecinfo = cc.find_library('libexecinfo', required: false)
|
|
|
|
if libexecinfo.found() and cc.has_header('execinfo.h')
|
2021-04-20 10:22:23 +00:00
|
|
|
add_project_link_arguments('-lexecinfo', language: 'c')
|
|
|
|
dpdk_extra_ldflags += '-lexecinfo'
|
2021-02-25 01:49:19 +00:00
|
|
|
endif
|
|
|
|
|
2019-05-02 16:51:54 +00:00
|
|
|
# check for libbsd
|
2021-01-18 14:29:57 +00:00
|
|
|
libbsd = dependency('libbsd', required: false, method: 'pkg-config')
|
2019-05-02 16:51:54 +00:00
|
|
|
if libbsd.found()
|
2021-04-20 10:22:23 +00:00
|
|
|
dpdk_conf.set('RTE_USE_LIBBSD', 1)
|
eal: support strlcpy function
The strncpy function is error prone for doing "safe" string copies, so
we generally try to use "snprintf" instead in the code. The function
"strlcpy" is a better alternative, since it better conveys the
intention of the programmer, and doesn't suffer from the non-null
terminating behaviour of it's n'ed brethern.
The downside of this function is that it is not available by default
on linux, though standard in the BSD's. It is available on most
distros by installing "libbsd" package.
This patch therefore provides the following in rte_string_fns.h to ensure
that strlcpy is available there:
* for BSD, include string.h as normal
* if RTE_USE_LIBBSD is set, include <bsd/string.h>
* if not set, fallback to snprintf for strlcpy
Using make build system, the RTE_USE_LIBBSD is a hard-coded value to "n",
but when using meson, it's automatically set based on what is available
on the platform.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
2018-03-12 11:32:59 +00:00
|
|
|
endif
|
|
|
|
|
2019-09-24 12:04:14 +00:00
|
|
|
# check for pcap
|
2020-10-09 14:19:14 +00:00
|
|
|
pcap_dep = dependency('libpcap', required: false, method: 'pkg-config')
|
|
|
|
if not pcap_dep.found()
|
2021-04-20 10:22:23 +00:00
|
|
|
# pcap got a pkg-config file only in 1.9.0
|
|
|
|
pcap_dep = cc.find_library('pcap', required: false)
|
2019-09-24 12:04:14 +00:00
|
|
|
endif
|
|
|
|
if pcap_dep.found() and cc.has_header('pcap.h', dependencies: pcap_dep)
|
2021-04-20 10:22:23 +00:00
|
|
|
dpdk_conf.set('RTE_PORT_PCAP', 1)
|
|
|
|
dpdk_extra_ldflags += '-lpcap'
|
2019-09-24 12:04:14 +00:00
|
|
|
endif
|
|
|
|
|
2020-04-19 10:01:01 +00:00
|
|
|
# for clang 32-bit compiles we need libatomic for 64-bit atomic ops
|
|
|
|
if cc.get_id() == 'clang' and dpdk_conf.get('RTE_ARCH_64') == false
|
2021-04-20 10:22:23 +00:00
|
|
|
atomic_dep = cc.find_library('atomic', required: true)
|
|
|
|
add_project_link_arguments('-latomic', language: 'c')
|
|
|
|
dpdk_extra_ldflags += '-latomic'
|
2020-04-19 10:01:01 +00:00
|
|
|
endif
|
|
|
|
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
# add -include rte_config to cflags
|
|
|
|
add_project_arguments('-include', 'rte_config.h', language: 'c')
|
|
|
|
|
|
|
|
# enable extra warnings and disable any unwanted warnings
|
|
|
|
warning_flags = [
|
2021-04-20 10:22:23 +00:00
|
|
|
# -Wall is added by meson by default, so add -Wextra only
|
|
|
|
'-Wextra',
|
|
|
|
|
|
|
|
# additional warnings in alphabetical order
|
|
|
|
'-Wcast-qual',
|
|
|
|
'-Wdeprecated',
|
|
|
|
'-Wformat',
|
|
|
|
'-Wformat-nonliteral',
|
|
|
|
'-Wformat-security',
|
|
|
|
'-Wmissing-declarations',
|
|
|
|
'-Wmissing-prototypes',
|
|
|
|
'-Wnested-externs',
|
|
|
|
'-Wold-style-definition',
|
|
|
|
'-Wpointer-arith',
|
|
|
|
'-Wsign-compare',
|
|
|
|
'-Wstrict-prototypes',
|
|
|
|
'-Wundef',
|
|
|
|
'-Wwrite-strings',
|
|
|
|
|
|
|
|
# globally disabled warnings
|
|
|
|
'-Wno-address-of-packed-member',
|
|
|
|
'-Wno-packed-not-aligned',
|
|
|
|
'-Wno-missing-field-initializers',
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
]
|
2020-05-14 13:18:57 +00:00
|
|
|
if cc.get_id() == 'gcc' and cc.version().version_compare('>=10.0')
|
|
|
|
# FIXME: Bugzilla 396
|
2021-04-20 10:22:23 +00:00
|
|
|
warning_flags += '-Wno-zero-length-bounds'
|
2020-05-14 13:18:57 +00:00
|
|
|
endif
|
2018-09-26 09:15:36 +00:00
|
|
|
if not dpdk_conf.get('RTE_ARCH_64')
|
2018-07-03 10:31:15 +00:00
|
|
|
# for 32-bit, don't warn about casting a 32-bit pointer to 64-bit int - it's fine!!
|
2021-04-20 10:22:23 +00:00
|
|
|
warning_flags += '-Wno-pointer-to-int-cast'
|
2018-07-03 10:31:15 +00:00
|
|
|
endif
|
2020-01-24 15:37:55 +00:00
|
|
|
if cc.get_id() == 'intel'
|
2021-04-20 10:22:23 +00:00
|
|
|
warning_ids = [181, 188, 2203, 2279, 2557, 3179, 3656]
|
|
|
|
foreach i:warning_ids
|
|
|
|
warning_flags += '-diag-disable=@0@'.format(i)
|
|
|
|
endforeach
|
2020-01-24 15:37:55 +00:00
|
|
|
endif
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
foreach arg: warning_flags
|
2021-04-20 10:22:23 +00:00
|
|
|
if cc.has_argument(arg)
|
|
|
|
add_project_arguments(arg, language: 'c')
|
|
|
|
endif
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
endforeach
|
|
|
|
|
2018-01-22 15:26:30 +00:00
|
|
|
# set other values pulled from the build options
|
|
|
|
dpdk_conf.set('RTE_MAX_LCORE', get_option('max_lcores'))
|
|
|
|
dpdk_conf.set('RTE_MAX_NUMA_NODES', get_option('max_numa_nodes'))
|
2019-02-07 15:53:17 +00:00
|
|
|
dpdk_conf.set('RTE_MAX_ETHPORTS', get_option('max_ethports'))
|
2018-01-22 15:26:30 +00:00
|
|
|
dpdk_conf.set('RTE_LIBEAL_USE_HPET', get_option('use_hpet'))
|
2020-04-22 19:03:19 +00:00
|
|
|
dpdk_conf.set('RTE_ENABLE_TRACE_FP', get_option('enable_trace_fp'))
|
2018-01-22 15:26:30 +00:00
|
|
|
# values which have defaults which may be overridden
|
|
|
|
dpdk_conf.set('RTE_MAX_VFIO_GROUPS', 64)
|
2018-05-16 16:44:53 +00:00
|
|
|
dpdk_conf.set('RTE_DRIVER_MEMPOOL_BUCKET_SIZE_KB', 64)
|
2018-07-03 10:31:16 +00:00
|
|
|
dpdk_conf.set('RTE_LIBRTE_DPAA2_USE_PHYS_IOVA', true)
|
2020-07-02 10:57:21 +00:00
|
|
|
if dpdk_conf.get('RTE_ARCH_64')
|
2021-04-20 10:22:23 +00:00
|
|
|
dpdk_conf.set('RTE_MAX_MEM_MB', 524288)
|
2020-07-02 10:57:21 +00:00
|
|
|
else # for 32-bit we need smaller reserved memory areas
|
2021-04-20 10:22:23 +00:00
|
|
|
dpdk_conf.set('RTE_MAX_MEM_MB', 2048)
|
2020-07-02 10:57:21 +00:00
|
|
|
endif
|
2018-01-22 15:26:30 +00:00
|
|
|
|
2018-09-26 09:15:36 +00:00
|
|
|
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
compile_time_cpuflags = []
|
2018-01-22 15:26:29 +00:00
|
|
|
subdir(arch_subdir)
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
dpdk_conf.set('RTE_COMPILE_TIME_CPUFLAGS', ','.join(compile_time_cpuflags))
|
|
|
|
|
2021-01-15 13:26:06 +00:00
|
|
|
# apply cross-specific options
|
|
|
|
if meson.is_cross_build()
|
2021-04-20 10:22:23 +00:00
|
|
|
# configure RTE_MAX_LCORE and RTE_MAX_NUMA_NODES from cross file
|
|
|
|
cross_max_lcores = meson.get_cross_property('max_lcores', 0)
|
|
|
|
if cross_max_lcores != 0
|
|
|
|
message('Setting RTE_MAX_LCORE from cross file')
|
|
|
|
dpdk_conf.set('RTE_MAX_LCORE', cross_max_lcores)
|
|
|
|
endif
|
|
|
|
cross_max_numa_nodes = meson.get_cross_property('max_numa_nodes', 0)
|
|
|
|
if cross_max_numa_nodes != 0
|
|
|
|
message('Setting RTE_MAX_NUMA_NODES from cross file')
|
|
|
|
dpdk_conf.set('RTE_MAX_NUMA_NODES', cross_max_numa_nodes)
|
|
|
|
endif
|
2021-01-15 13:26:06 +00:00
|
|
|
endif
|
|
|
|
|
build: add infrastructure for meson and ninja builds
To build with meson and ninja, we need some initial infrastructure in
place. The build files for meson always need to be called "meson.build",
and options get placed in meson_options.txt
This commit adds a top-level meson.build file, which sets up the global
variables for tracking drivers, libraries, etc., and then includes other
build files, before finishing by writing the global build configuration
header file and a DPDK pkgconfig file at the end, using some of those same
globals.
From the top level build file, the only include file thus far is for the
config folder, which does some other setup of global configuration
parameters, including pulling in architecture specific parameters from an
architectural subdirectory. A number of configuration build options are
provided for the project to tune a number of global variables which will be
used later e.g. max numa nodes, max cores, etc. These settings all make
their way to the global build config header "rte_build_config.h". There is
also a file "rte_config.h", which includes "rte_build_config.h", and this
file is meant to hold other build-time values which are present in our
current static build configuration but are not normally meant for
user-configuration. Ideally, over time, the values placed here should be
moved to the individual libraries or drivers which want those values.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com>
Acked-by: Keith Wiles <keith.wiles@intel.com>
Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
|
|
|
# set the install path for the drivers
|
|
|
|
dpdk_conf.set_quoted('RTE_EAL_PMD_PATH', eal_pmd_path)
|
|
|
|
|
2020-12-09 17:14:20 +00:00
|
|
|
install_headers(['rte_config.h'],
|
2021-04-20 10:22:23 +00:00
|
|
|
subdir: get_option('include_subdir_arch'))
|
2018-10-04 14:09:58 +00:00
|
|
|
|
|
|
|
# enable VFIO only if it is linux OS
|
2019-04-09 10:55:36 +00:00
|
|
|
dpdk_conf.set('RTE_EAL_VFIO', is_linux)
|
2019-05-14 14:04:16 +00:00
|
|
|
|
|
|
|
# specify -D_GNU_SOURCE unconditionally
|
|
|
|
add_project_arguments('-D_GNU_SOURCE', language: 'c')
|
|
|
|
|
|
|
|
# specify -D__BSD_VISIBLE for FreeBSD
|
|
|
|
if is_freebsd
|
2021-04-20 10:22:23 +00:00
|
|
|
add_project_arguments('-D__BSD_VISIBLE', language: 'c')
|
2019-05-14 14:04:16 +00:00
|
|
|
endif
|
2019-11-07 15:03:09 +00:00
|
|
|
|
2020-02-27 04:25:34 +00:00
|
|
|
if is_windows
|
2021-04-20 10:22:23 +00:00
|
|
|
# VirtualAlloc2() is available since Windows 10 / Server 2016.
|
|
|
|
add_project_arguments('-D_WIN32_WINNT=0x0A00', language: 'c')
|
2020-02-27 04:25:34 +00:00
|
|
|
|
2021-04-20 10:22:23 +00:00
|
|
|
# Use MinGW-w64 stdio, because DPDK assumes ANSI-compliant formatting.
|
|
|
|
if cc.get_id() == 'gcc'
|
|
|
|
add_project_arguments('-D__USE_MINGW_ANSI_STDIO', language: 'c')
|
|
|
|
endif
|
2020-06-15 00:43:53 +00:00
|
|
|
|
2021-04-20 10:22:23 +00:00
|
|
|
# Disable secure CRT deprecated warnings for clang
|
|
|
|
if cc.get_id() == 'clang'
|
|
|
|
add_project_arguments('-D_CRT_SECURE_NO_WARNINGS', language: 'c')
|
|
|
|
endif
|
2020-11-29 16:00:24 +00:00
|
|
|
|
2021-04-20 10:22:23 +00:00
|
|
|
add_project_link_arguments('-lws2_32', language: 'c')
|
2020-09-28 21:50:51 +00:00
|
|
|
|
2021-04-20 10:22:23 +00:00
|
|
|
# Contrary to docs, VirtualAlloc2() is exported by mincore.lib
|
|
|
|
# in Windows SDK, while MinGW exports it by advapi32.a.
|
|
|
|
if is_ms_linker
|
|
|
|
add_project_link_arguments('-lmincore', language: 'c')
|
|
|
|
endif
|
2020-06-15 00:43:54 +00:00
|
|
|
|
2021-04-20 10:22:23 +00:00
|
|
|
add_project_link_arguments('-ladvapi32', '-lsetupapi', language: 'c')
|
|
|
|
add_project_link_arguments('-ldbghelp', language: 'c')
|
2020-02-27 04:25:34 +00:00
|
|
|
endif
|
|
|
|
|
2019-11-07 15:03:09 +00:00
|
|
|
if get_option('b_lto')
|
2021-04-20 10:22:23 +00:00
|
|
|
if cc.has_argument('-ffat-lto-objects')
|
|
|
|
add_project_arguments('-ffat-lto-objects', language: 'c')
|
|
|
|
else
|
|
|
|
error('compiler does not support fat LTO objects - please turn LTO off')
|
|
|
|
endif
|
|
|
|
# workaround for gcc bug 81440
|
|
|
|
if cc.get_id() == 'gcc' and cc.version().version_compare('<8.0')
|
|
|
|
add_project_arguments('-Wno-lto-type-mismatch', language: 'c')
|
|
|
|
add_project_link_arguments('-Wno-lto-type-mismatch', language: 'c')
|
|
|
|
endif
|
2019-11-07 15:03:09 +00:00
|
|
|
endif
|
2021-01-11 13:55:59 +00:00
|
|
|
|
|
|
|
if get_option('default_library') == 'both'
|
2021-04-20 10:22:23 +00:00
|
|
|
error( '''
|
|
|
|
Unsupported value "both" for "default_library" option.
|
2021-01-11 13:55:59 +00:00
|
|
|
|
2021-04-20 10:22:23 +00:00
|
|
|
NOTE: DPDK always builds both shared and static libraries. Please set
|
|
|
|
"default_library" to either "static" or "shared" to select default linkage
|
|
|
|
for apps and any examples.''')
|
2021-01-11 13:55:59 +00:00
|
|
|
endif
|