Re: regression in meson build, AC_PATH_PROG lost
Am Thu, 12 Nov 2020 22:40:02 +0100
schrieb Olaf Hering <olaf(a)aepfle.de>:
AC_PATH_PROG([PARTED], [parted], [], [$LIBVIRT_SBIN_PATH])
Is there a consensus now how to address this?
From what I understand, using just exec(BASENAME) to search for the
binary in PATH is acceptable. It may result in surprises on systems which have BASENAME in
/usr/local/*bin. Previously the absolute path at build time was used. I think this can be
tolerated.
Should there be a list of each called binary in meson.build? This would at least give some
hint about what might be called at runtime, even if the result of find_program() will not
be stored in the resulting libvirt binaries.
Olaf
Attachments:
- attachment.sig (application/pgp-signature — 833 bytes)