Widespread issues with empty PKG_CONFIG
Too many projects' configure
scripts don't check for empty PKG_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 set PKG_CONFIG=false
, so that calls result in a fail without bogus errors.
In order to support both scenarios, I propose the PKG_PROG_PKG_CONFIG
macro:
- by default abort the configure script.
- take an extra (optional) argument to specify a custom action instead.