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
|
|
|
|
|
|
|
# for checking defines we need to use the correct compiler flags
|
2019-01-17 17:17:44 +00:00
|
|
|
march_opt = ['-march=@0@'.format(machine)]
|
|
|
|
|
|
|
|
# get binutils version for the workaround of Bug 97
|
2019-04-09 10:55:36 +00:00
|
|
|
if not is_windows
|
2019-04-02 03:54:49 +00:00
|
|
|
ldver = run_command('ld', '-v').stdout().strip()
|
|
|
|
if ldver.contains('2.30')
|
|
|
|
if cc.has_argument('-mno-avx512f')
|
|
|
|
march_opt += '-mno-avx512f'
|
|
|
|
message('Binutils 2.30 detected, disabling AVX512 support as workaround for bug #97')
|
|
|
|
endif
|
2019-01-17 17:17:44 +00:00
|
|
|
endif
|
|
|
|
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
|
|
|
|
|
|
|
# we require SSE4.2 for DPDK
|
|
|
|
sse_errormsg = '''SSE4.2 instruction set is required for DPDK.
|
|
|
|
Please set the machine type to "nehalem" or "corei7" or higher value'''
|
|
|
|
|
|
|
|
if cc.get_define('__SSE4_2__', args: march_opt) == ''
|
|
|
|
error(sse_errormsg)
|
|
|
|
endif
|
|
|
|
|
2017-09-14 11:11:20 +00:00
|
|
|
base_flags = ['SSE', 'SSE2', 'SSE3','SSSE3', 'SSE4_1', 'SSE4_2']
|
|
|
|
foreach f:base_flags
|
|
|
|
dpdk_conf.set('RTE_MACHINE_CPUFLAG_' + f, 1)
|
|
|
|
compile_time_cpuflags += ['RTE_CPUFLAG_' + f]
|
|
|
|
endforeach
|
|
|
|
|
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_ARCH_X86', 1)
|
2018-09-26 09:15:36 +00:00
|
|
|
if dpdk_conf.get('RTE_ARCH_64')
|
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_ARCH_X86_64', 1)
|
|
|
|
dpdk_conf.set('RTE_ARCH', 'x86_64')
|
|
|
|
else
|
|
|
|
dpdk_conf.set('RTE_ARCH_I686', 1)
|
|
|
|
dpdk_conf.set('RTE_ARCH', 'i686')
|
|
|
|
endif
|
|
|
|
|
|
|
|
if cc.get_define('__AES__', args: march_opt) != ''
|
|
|
|
dpdk_conf.set('RTE_MACHINE_CPUFLAG_AES', 1)
|
|
|
|
compile_time_cpuflags += ['RTE_CPUFLAG_AES']
|
|
|
|
endif
|
|
|
|
if cc.get_define('__PCLMUL__', args: march_opt) != ''
|
|
|
|
dpdk_conf.set('RTE_MACHINE_CPUFLAG_PCLMULQDQ', 1)
|
|
|
|
compile_time_cpuflags += ['RTE_CPUFLAG_PCLMULQDQ']
|
|
|
|
endif
|
|
|
|
if cc.get_define('__AVX__', args: march_opt) != ''
|
|
|
|
dpdk_conf.set('RTE_MACHINE_CPUFLAG_AVX', 1)
|
|
|
|
compile_time_cpuflags += ['RTE_CPUFLAG_AVX']
|
|
|
|
endif
|
|
|
|
if cc.get_define('__AVX2__', args: march_opt) != ''
|
|
|
|
dpdk_conf.set('RTE_MACHINE_CPUFLAG_AVX2', 1)
|
|
|
|
compile_time_cpuflags += ['RTE_CPUFLAG_AVX2']
|
|
|
|
endif
|
2017-09-14 11:11:20 +00:00
|
|
|
if cc.get_define('__AVX512F__', args: march_opt) != ''
|
|
|
|
dpdk_conf.set('RTE_MACHINE_CPUFLAG_AVX512F', 1)
|
|
|
|
compile_time_cpuflags += ['RTE_CPUFLAG_AVX512F']
|
|
|
|
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_CACHE_LINE_SIZE', 64)
|