2017-08-27 18:42:21 +01:00
|
|
|
|
mesonConfigurePhase() {
|
|
|
|
|
|
runHook preConfigure
|
|
|
|
|
|
|
2019-10-30 15:16:20 +00:00
|
|
|
|
if [ -z "${dontAddPrefix-}" ]; then
|
2017-08-27 18:42:21 +01:00
|
|
|
|
mesonFlags="--prefix=$prefix $mesonFlags"
|
|
|
|
|
|
fi
|
|
|
|
|
|
|
2018-03-05 06:08:18 +00:00
|
|
|
|
# See multiple-outputs.sh and meson’s coredata.py
|
|
|
|
|
|
mesonFlags="\
|
|
|
|
|
|
--libdir=${!outputLib}/lib --libexecdir=${!outputLib}/libexec \
|
|
|
|
|
|
--bindir=${!outputBin}/bin --sbindir=${!outputBin}/sbin \
|
|
|
|
|
|
--includedir=${!outputInclude}/include \
|
|
|
|
|
|
--mandir=${!outputMan}/share/man --infodir=${!outputInfo}/share/info \
|
|
|
|
|
|
--localedir=${!outputLib}/share/locale \
|
2019-06-19 02:17:42 +01:00
|
|
|
|
-Dauto_features=${mesonAutoFeatures:-enabled} \
|
2019-06-19 02:47:25 +01:00
|
|
|
|
-Dwrap_mode=${mesonWrapMode:-nodownload} \
|
2018-03-05 06:08:18 +00:00
|
|
|
|
$mesonFlags"
|
|
|
|
|
|
|
2019-06-19 02:48:05 +01:00
|
|
|
|
mesonFlags="${crossMesonFlags+$crossMesonFlags }--buildtype=${mesonBuildType:-plain} $mesonFlags"
|
2017-08-27 18:42:21 +01:00
|
|
|
|
|
|
|
|
|
|
echo "meson flags: $mesonFlags ${mesonFlagsArray[@]}"
|
|
|
|
|
|
|
2022-09-27 09:04:01 +01:00
|
|
|
|
meson setup build $mesonFlags "${mesonFlagsArray[@]}"
|
2017-08-27 18:42:21 +01:00
|
|
|
|
cd build
|
|
|
|
|
|
|
2017-12-02 06:49:59 +00:00
|
|
|
|
if ! [[ -v enableParallelBuilding ]]; then
|
|
|
|
|
|
enableParallelBuilding=1
|
|
|
|
|
|
echo "meson: enabled parallel building"
|
|
|
|
|
|
fi
|
|
|
|
|
|
|
meson.setupHook: prefer meson commands over ninja
Meson now comes with its own set of commands for building, testing,
installing etc., that by default wrap around Ninja. The reason to
prefer using the Meson commands is that they take additional
options (e.g. setting custom timeouts for tests — my motivation for
this change).
Here, I've modified the Meson setup hook so that Meson's test and
install commands will be used instead of Ninja's when Meson's
configurePhase is used. This restriction is to avoid starting to run
Meson directly when dealing with custom build systems that wrap around
Meson, like QEMU's. We don't use meson's compile command, as it just
runs ninja, and that's handled fine by the existing Ninja setup hook.
Naturally the Meson commands don't support entirely the same set of
options that the Ninja ones did, but I checked through Nixpkgs to find
any packages using Meson that used any options that wouldn't be picked
up by this new system. I only found one, and it was just setting
checkTarget = "test", which is the default value for Ninja and has no
Meson equivalent (because we directly tell Meson to run the tests
rather than going through a generic job system like Ninja).
Link: https://github.com/NixOS/nixpkgs/issues/113829
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
2023-10-06 09:09:52 +01:00
|
|
|
|
if [[ ${checkPhase-ninjaCheckPhase} = ninjaCheckPhase && -z $dontUseMesonCheck ]]; then
|
|
|
|
|
|
checkPhase=mesonCheckPhase
|
|
|
|
|
|
fi
|
|
|
|
|
|
if [[ ${installPhase-ninjaInstallPhase} = ninjaInstallPhase && -z $dontUseMesonInstall ]]; then
|
|
|
|
|
|
installPhase=mesonInstallPhase
|
2023-02-21 19:50:48 +00:00
|
|
|
|
fi
|
|
|
|
|
|
|
2017-08-27 18:42:21 +01:00
|
|
|
|
runHook postConfigure
|
|
|
|
|
|
}
|
|
|
|
|
|
|
meson.setupHook: prefer meson commands over ninja
Meson now comes with its own set of commands for building, testing,
installing etc., that by default wrap around Ninja. The reason to
prefer using the Meson commands is that they take additional
options (e.g. setting custom timeouts for tests — my motivation for
this change).
Here, I've modified the Meson setup hook so that Meson's test and
install commands will be used instead of Ninja's when Meson's
configurePhase is used. This restriction is to avoid starting to run
Meson directly when dealing with custom build systems that wrap around
Meson, like QEMU's. We don't use meson's compile command, as it just
runs ninja, and that's handled fine by the existing Ninja setup hook.
Naturally the Meson commands don't support entirely the same set of
options that the Ninja ones did, but I checked through Nixpkgs to find
any packages using Meson that used any options that wouldn't be picked
up by this new system. I only found one, and it was just setting
checkTarget = "test", which is the default value for Ninja and has no
Meson equivalent (because we directly tell Meson to run the tests
rather than going through a generic job system like Ninja).
Link: https://github.com/NixOS/nixpkgs/issues/113829
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
2023-10-06 09:09:52 +01:00
|
|
|
|
mesonCheckPhase() {
|
|
|
|
|
|
runHook preCheck
|
|
|
|
|
|
|
|
|
|
|
|
local flagsArray=($mesonCheckFlags "${mesonCheckFlagsArray[@]}")
|
|
|
|
|
|
|
|
|
|
|
|
echoCmd 'check flags' "${flagsArray[@]}"
|
|
|
|
|
|
meson test --no-rebuild "${flagsArray[@]}"
|
|
|
|
|
|
|
|
|
|
|
|
runHook postCheck
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
mesonInstallPhase() {
|
|
|
|
|
|
runHook preInstall
|
|
|
|
|
|
|
|
|
|
|
|
# shellcheck disable=SC2086
|
|
|
|
|
|
local flagsArray=($mesonInstallFlags "${mesonInstallFlagsArray[@]}")
|
|
|
|
|
|
|
|
|
|
|
|
echoCmd 'install flags' "${flagsArray[@]}"
|
|
|
|
|
|
meson install --no-rebuild "${flagsArray[@]}"
|
|
|
|
|
|
|
|
|
|
|
|
runHook postInstall
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2019-10-31 17:59:18 +00:00
|
|
|
|
if [ -z "${dontUseMesonConfigure-}" -a -z "${configurePhase-}" ]; then
|
2017-08-27 18:42:21 +01:00
|
|
|
|
setOutputFlags=
|
|
|
|
|
|
configurePhase=mesonConfigurePhase
|
|
|
|
|
|
fi
|
