Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support pkg-config builds #552

Open
tbussmann opened this issue Jan 23, 2020 · 2 comments
Open

Support pkg-config builds #552

tbussmann opened this issue Jan 23, 2020 · 2 comments

Comments

@tbussmann
Copy link
Member

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.

@jakob
Copy link
Member

jakob commented Jan 25, 2020

This sounds like a good idea. Could adding those files break anything? If not, we could probably include them with the next scheduled release (Feb 13)

@jakob
Copy link
Member

jakob commented May 14, 2020

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants