25 |
notation, without getting builddir pathnames ever mentioned in .la |
notation, without getting builddir pathnames ever mentioned in .la |
26 |
files that get installed. |
files that get installed. |
27 |
|
|
28 |
|
* Eric Lemings <elemings@cyberia.lemings.com> writes: |
29 |
|
Because of a growing number of config scripts for packages in GNOME 1.2 |
30 |
|
(e.g. glib-config, xml-config, orbit-config. etc), development of GNOME |
31 |
|
2.0 spawned a separate tool called pkg-config that allows all packages |
32 |
|
to use one tool rather than several different scripts to query compile |
33 |
|
flags, link flags, and other configuration data. |
34 |
|
|
35 |
|
The functionality of pkg-config seems to me to have a lot of overlap |
36 |
|
with the goals of libtool. I was wondering if anyone had considered |
37 |
|
adding an eighth mode to libtool that just queries the installed |
38 |
|
library for the same information that pkg-config provides. Since |
39 |
|
most packages that use pkg-config also use libtool, I think this |
40 |
|
would be a good way to reduce maintainer and developer dependencies. |
41 |
|
|
42 |
|
|
43 |
In the future: |
In the future: |
44 |
************** |
************** |
45 |
|
|