| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pkg-config files for libpq and ecpg |
| Date: | 2013-01-15 19:16:01 |
| Message-ID: | 50F5AAF1.3070607@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I'll take another stab at providing pkg-config files for the client-side
libraries.
The main reason this time around is that this works a lot better (or at
all) for multi-arch library installations.
Another is that pkg-config has become a lot smarter and flexible over
the years, and it's probably a better choice for users who are already
used to its interface. There is a lot of confusion, for example, about
what pg_config --libs really means. We often evade that by saying,
well, those are the libraries we linked with, but there is a lack of
clarity in that context about what libraries a user should link with.
The way it's implemented, it doesn't require manual maintenance, so it
should not be much of a bother.
A side issue that arose: libecpg_compat is linked with libpq, but
doesn't seem to use it. This was added many years ago in
cd75f94dafd43358305811b7576ad75d889097e3, but it doesn't appear to be
required anymore. Needs some checking.
| Attachment | Content-Type | Size |
|---|---|---|
| pg-pkg-config.patch | text/plain | 4.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-01-15 19:16:38 | Re: count(*) of zero rows returns 1 |
| Previous Message | Bruce Momjian | 2013-01-15 19:11:23 | Re: buffer assertion tripping under repeat pgbench load |