[dpdk-dev] [PATCH v4] devtools: add test script for meson builds
Bruce Richardson
bruce.richardson at intel.com
Mon May 28 11:39:18 CEST 2018
On Sat, May 26, 2018 at 01:21:42PM +0200, Thomas Monjalon wrote:
> From: Bruce Richardson <bruce.richardson at intel.com>
>
> To simplify testing with the meson and ninja builds, we can add a script
> to set up and do multiple builds. Currently this script sets up:
>
> * clang and gcc builds
> * builds using static and shared linkage for binaries (libs are always
> built as both)
> * a build using the lowest instruction-set level for x86 (-march=nehalem)
> * cross-builds for each cross-file listed in config/arm
>
> Each build is configured in a directory ending in *-build, and then for
> the build stage, we just call ninja in each directory in turn. [i.e. we
> assume every directory starting with "build-" is a meson build, which is
> probably an ok assumption].
>
> Signed-off-by: Bruce Richardson <bruce.richardson at intel.com>
> Signed-off-by: Thomas Monjalon <thomas at monjalon.net>
> ---
> v2: it is a rework with 3 major changes
> - automatically stop on error thanks to -e
> - directory name starts with "build-"
> - optionally load a config file to get some environment variables
> v3:
> - remove forcing "cd": use current directory
> - remove CROSS: use hard-written aarch64-linux-gnu-gcc
> - remove config load in script start
> v4:
> - remove config file loading (will be improved and sent later)
> - the v4 is closer to what Bruce sent as v1
> ---
Yes, it's closer, but there is also some good material in your v2 that we
probably want to rework into this later on. I suggest in the name of
progress we merge this version and iterate on improving it later.
/Bruce
More information about the dev
mailing list