| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | phoemix(at)harmless(dot)hu (Czuczy Gergely), Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: added pkg-config script |
| Date: | 2004-08-22 19:54:24 |
| Message-ID: | 200408222154.24118.peter_e@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Czuczy Gergely wrote:
> pkg-config is a relatively new method, but most packages
> (like gtk, silc's debian package, sqlite, alsa, atk, fontconfig,
> freetype2, gdk-*, glib, gthread, libexslt, libpng, openssl, pango,
> sigc++, xft, etc) support it,
That sounds very GNOME-biased, and the list on my machine supports that.
So it's far from universal.
> because it's prefferd, doesn't have
> non-standard behaviour(like php-config, doesn't have --cflags, it has
> --includes instead).
It depends on what you define as standard. pkg-config doesn't have a
--cppflags option, only --cflags, so I'm already wondering how one can
write correct makefiles with it.
> there are hundred millions of configure script that cannot
> decide how to get postgres' cflags and libs by themselves.
That's nonsense. pg_config is successfully used to interface to
PostgreSQL libraries.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Czuczy Gergely | 2004-08-22 19:57:26 | Re: added pkg-config script |
| Previous Message | Czuczy Gergely | 2004-08-22 19:29:22 | Re: added pkg-config script |