Andres Freund <andres@anarazel.de> writes:
> Yea. They might not be independent of where you get other dependencies from
> though. Does macports install headers / libraries into a path that's found by
> default? Or does one have to pass --with-includes / --with-libs to configure
> and set PKG_CONFIG_PATH, like with homebrew?
What are you expecting to need PKG_CONFIG_PATH for? Or more precisely,
why would meson/ninja create any new need for that that doesn't exist
in the autoconf case?
regards, tom lane