diff options
| author | Peter Waller <p@pwaller.net> | 2024-09-15 11:37:03 +0100 |
|---|---|---|
| committer | Peter Waller <p@pwaller.net> | 2024-09-15 11:50:52 +0100 |
| commit | 290ec4e775b7ebb6ff2a882ef0b836171a761bc3 (patch) | |
| tree | da20eabd7cc4ad85050bace3df0a8352b4189c05 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch | |
| parent | 755459a3efd4ed55c7bf65f53104952ce312ffc7 (diff) | |
llvmPackages.*: Add devExtraCmakeFlags parameter
cmake flags have a 'last flag wins' logic, so by appending to the end of
the flags it is possible to override any cmake flag.
It also ignores (and warns) if a flag is unused, so passing flags across
all packages should be safe if you want to target one package.
In combination with #320261, this PR allows consistently overriding all
packages within LLVM with additional cmake arguments. Consistency here
means for example 'if you override LLVM, then all dependencies on it are
also see the overridden LLVM in their input'. Consistency is hard to
achieve with the other obvious way of implementing this as a user: if
you use overrideAttrs then you have to write a big mess of override code
in order to override all dependents, and this can be very difficult in a
cross-compilation scenario using crossSystem and useLLVM, for example.
With this PR it is possible to write an overlay which overlays
`llvmPackages` with `llvmPackage.override { devExtraCmakeFlags = [ ... ]; }`,
and then the toolchain used with useLLVM in effect should respect
these flags.
This is useful in development for experimenting with the effect of
various flags, hence the chosen name `devCmakeFlags`.
This won't work out of the box without #341855 applied, which fixes
override passthrough.
See-Also: #320261, #341855
Signed-off-by: Peter Waller <p@pwaller.net>
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions
