You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently support building extensions and compiling against the libraries of PostgresApp by providing a working pg_config. However there is a second supported way using pkg-config, however we do exclude the $(PREFIX)/lib/pkgconfig folder during packaging in CopyBinaries.sh. Would it make sense to include that? Users could than run pkg-config-based builds with PKG_CONFIG_PATH=/Applications/Postgres.app/Contents/Versions/latest/lib/pkgconfig against PostgresApp.
The text was updated successfully, but these errors were encountered:
I forgot about this, but I do want to follow up on this.
Should we include all pkg-config for all libraries that we ship, or just for some of them? We also include things like OpenSSL. Do we want other software to link to our OpenSSL? Or should we just include the pkg-config file for libpq?
We currently support building extensions and compiling against the libraries of PostgresApp by providing a working
pg_config
. However there is a second supported way usingpkg-config
, however we do exclude the$(PREFIX)/lib/pkgconfig
folder during packaging inCopyBinaries.sh
. Would it make sense to include that? Users could than runpkg-config
-based builds withPKG_CONFIG_PATH=/Applications/Postgres.app/Contents/Versions/latest/lib/pkgconfig
against PostgresApp.The text was updated successfully, but these errors were encountered: