Widespread issues with empty PKG_CONFIG #350
Comments
ismaell
added a commit
to ismaell/pkgconf
that referenced
this issue
Apr 1, 2024
Provide a second optional argument to PKG_PROG_PKG_CONFIG with an action to take if no pkgconf is found, and default to aborting. Too many configure scripts in the wild don't handle an empty PKG_CONFIG, resulting in weird error messages through the run, which often confuse users. Authors wishing to fallback to other methods can either return to the old behavior by specifying [:] as an action, or use [PKG_CONFIG=false] and call pkg-config macros normally, handling the fallback as any other failure. Users can override PKG_CONFIG in the command line so this should imply no regression. Closes: pkgconf#350 Ref: https://gitlab.freedesktop.org/pkg-config/pkg-config/-/issues/69 Signed-off-by: Ismael Luceno <ismael@iodev.co.uk>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Too many projects'
configurescripts don't check for emptyPKG_CONFIG, yet use the variable directly, resulting in weird error messages through the run, which often confuse users. It would be useful to either error-out or setPKG_CONFIG=false, so that calls result in a fail without bogus errors.In order to support both scenarios, I propose the
PKG_PROG_PKG_CONFIGmacro:The text was updated successfully, but these errors were encountered: