diff options
| author | Daniel P. Berrangé <berrange@redhat.com> | 2025-04-25 13:17:12 +0100 |
|---|---|---|
| committer | Thomas Huth <thuth@redhat.com> | 2025-04-30 20:44:01 +0200 |
| commit | 6b1c744ec0d66d6d568f9a156282153fc11a21cf (patch) | |
| tree | 2ef1786d898e89d629c4ab34ad211c125ec2671e /scripts/rust/rustc_args.py | |
| parent | 55a494e53e1f0c73ba5cfb1b072fed9035b7961b (diff) | |
| download | qemu-6b1c744ec0d66d6d568f9a156282153fc11a21cf.zip qemu-6b1c744ec0d66d6d568f9a156282153fc11a21cf.tar.gz qemu-6b1c744ec0d66d6d568f9a156282153fc11a21cf.tar.bz2 | |
meson/configure: add 'valgrind' option & --{en, dis}able-valgrind flag
Currently valgrind debugging support for coroutine stacks is enabled
unconditionally when valgrind/valgrind.h is found. There is no way
to disable valgrind support if valgrind.h is present in the build env.
This is bad for distros, as an dependency far down the chain may cause
valgrind.h to become installed, inadvertently enabling QEMU's valgrind
debugging support. It also means if a distro wants valgrind support
there is no way to mandate this.
The solution is to add a 'valgrind' build feature to meson and thus
configure script.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-ID: <20250425121713.1913424-1-berrange@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Diffstat (limited to 'scripts/rust/rustc_args.py')
0 files changed, 0 insertions, 0 deletions