| 777014e5 | 02-Feb-2020 |
David Marchand <[email protected]> |
devtools: add ABI checks
For normal developers, those checks are disabled.
Enabling them requires a configuration that will trigger the ABI dumps generation as part of the existing devtools/test-bu
devtools: add ABI checks
For normal developers, those checks are disabled.
Enabling them requires a configuration that will trigger the ABI dumps generation as part of the existing devtools/test-build.sh and devtools/test-meson-builds.sh scripts.
Those checks are enabled in the CI for the default meson options on x86 and aarch64 so that proposed patches are validated via our CI robot. A cache of the ABI is stored in travis jobs to avoid rebuilding too often.
Checks can be informational only, by setting ABI_CHECKS_WARN_ONLY when breaking the ABI in a future release.
Explicit suppression rules have been added on internal structures exposed to crypto drivers as the current ABI policy does not apply to them. This could be improved in the future by carefully splitting the headers content with application and driver "users" in mind.
We currently have issues reported for librte_crypto recent changes for which suppression rules have been added too.
Mellanox glue libraries are explicitly skipped as they are not part of the application ABI.
Signed-off-by: David Marchand <[email protected]> Acked-by: Luca Boccassi <[email protected]>
show more ...
|
| aa759955 | 27-Nov-2019 |
Bruce Richardson <[email protected]> |
devtools: control location of test builds
By default, both test-build.sh and test-meson-builds.sh scripts create the builds they generate in the current working directory, leading to a large number
devtools: control location of test builds
By default, both test-build.sh and test-meson-builds.sh scripts create the builds they generate in the current working directory, leading to a large number of build directories being present when testing patches. This patchset modifies both scripts to use a DPDK_BUILD_TEST_DIR environment variable to control where the build outputs are put.
For example, doing: export DPDK_BUILD_TEST_DIR=__builds ./devtools/test-meson-builds.sh && ./devtools/test-build.sh \ x86_64-native-linux-clang+shared i686-native-linux-gcc
gives a "__builds" directory with 14 meson and 2 make builds (with the meson build count depending on compiler availability)
Signed-off-by: Bruce Richardson <[email protected]> Signed-off-by: Thomas Monjalon <[email protected]> Acked-by: David Marchand <[email protected]>
show more ...
|
| 7a8735e2 | 08-Oct-2019 |
David Marchand <[email protected]> |
devtools: check coverity and bugzilla tags
Let's try to check for discrepancies in coverity and bugzilla tags. The contributing guide specifies that: - for coverity issues, the tag is 'Coverity issu
devtools: check coverity and bugzilla tags
Let's try to check for discrepancies in coverity and bugzilla tags. The contributing guide specifies that: - for coverity issues, the tag is 'Coverity issue:' - for bugzilla issues, the tag is 'Bugzilla ID:'
Signed-off-by: David Marchand <[email protected]> Acked-by: Kevin Traynor <[email protected]>
show more ...
|
| 6b01864c | 22-Nov-2019 |
Ferruh Yigit <[email protected]> |
mk: remove library search path from binary
This patch functionally reverts the patch in fixes line to not have any hardcoded library path in the final binary for the security reasons, in case this b
mk: remove library search path from binary
This patch functionally reverts the patch in fixes line to not have any hardcoded library path in the final binary for the security reasons, in case this binary distributed to production environment.
RPATH only added in RTE_DEVEL_BUILD case and this binary shouldn't distributed, but still removing it to be cautious.
Fixes: 8919f73bcbaa ("mk: add build directory to library search path") Cc: [email protected]
Suggested-by: Bruce Richardson <[email protected]> Signed-off-by: Ferruh Yigit <[email protected]>
show more ...
|
| bd253daa | 14-Sep-2019 |
Thomas Monjalon <[email protected]> |
devtools: fix test of ninja install
When trying to compile some examples with libdpdk.pc, the right environment (for default target) was not loaded. The consequence is to not detect some dependencie
devtools: fix test of ninja install
When trying to compile some examples with libdpdk.pc, the right environment (for default target) was not loaded. The consequence is to not detect some dependencies because of missing directories in PKG_CONFIG_PATH.
The environment preparation is moved to a dedicate function, and called for the default target (cc), before testing the install output of the default build.
Fixes: 272236741258 ("devtools: load target-specific compilation environment")
Signed-off-by: Thomas Monjalon <[email protected]>
show more ...
|
| 54a88d1b | 13-Sep-2019 |
Thomas Monjalon <[email protected]> |
devtools: fix check of ccache for meson build
The meson build test fails if ccache is not available. The use of ccache must be optional. And if used, the compiler to check is the last word of $CC.
devtools: fix check of ccache for meson build
The meson build test fails if ccache is not available. The use of ccache must be optional. And if used, the compiler to check is the last word of $CC.
Fixes: e0ae780e6569 ("devtools: test compiler availability only once")
Signed-off-by: Thomas Monjalon <[email protected]> Acked-by: Luca Boccassi <[email protected]>
show more ...
|
| 27223674 | 12-Aug-2019 |
Thomas Monjalon <[email protected]> |
devtools: load target-specific compilation environment
In order to re-use the same test environment as with test-build.sh, the configuration file is loaded at each build, after adjusting the variabl
devtools: load target-specific compilation environment
In order to re-use the same test environment as with test-build.sh, the configuration file is loaded at each build, after adjusting the variable DPDK_TARGET.
This is especially useful to set the variable PKG_CONFIG_PATH, or define some meson options (without -D) in DPDK_MESON_OPTIONS.
The DPDK_TARGET values can be aarch64-*, powerpc64-*, x86_64-*. The matching DPDK_TARGET values for test-build.sh are arm64-*, ppc_64-*, x86_64-*. The advised expressions to use in the common configuration file are: if echo $DPDK_TARGET | grep -q '^a.*64-' ; then elif echo $DPDK_TARGET | grep -q '^p.*pc.*64' ; then elif echo $DPDK_TARGET | grep -q '^x86_64' ; then fi
Signed-off-by: Thomas Monjalon <[email protected]> Acked-by: Luca Boccassi <[email protected]>
show more ...
|