* Russ Allbery schrieb:
> pkg-config is much superior to libtool, since libtool includes all the
> libraries on dynamic links as well, which creates unwanted shared library
> dependencies and causes other problems. Because of that, the trend in
> Debian is to empty that information from libtool
]] Simon McVittie
| On Sat, 20 Nov 2010 at 21:58:56 +0100, Tollef Fog Heen wrote:
| > | Upstreams are only meant to change the .pc filename when they make an
| > | incompatible change to the API
| >
| > This seems to be the trend, but there's nothing in pkg-config's policies
| > or best practice
Dmitry Katsubo writes:
> Russ, thank you for comments. To answer your question I quote only one
> important section from the document I've referred:
> === quote ===
> 3.2.4 pkg-config File
> Many libraries deliver a .pc file for use by the pkg-config helper
> utility, which aids other libraries
On Mon, 22 Nov 2010 at 16:18:52 +0100, Dmitry Katsubo wrote:
> On 19.11.2010 22:51, Russ Allbery wrote:
> > Dmitry Katsubo writes:
> >> * Some libraries (e.g.) do not follow the agreement for .NET/CLI
> >> (http://pkg-mono.alioth.debian.org/cli-policy/ch-packaging.html#s-pkg-config-file)
> >> whic
On 19.11.2010 22:51, Russ Allbery wrote:
> Dmitry Katsubo writes:
>
>> The first problem I faced is that it is difficult to explore what should
>> be the list of libraries for static linking (as I have to provide the
>> list of libraries which are direct dependencies as well as indirect). I
>> kn
On Sat, 20 Nov 2010 at 21:58:56 +0100, Tollef Fog Heen wrote:
> | Upstreams are only meant to change the .pc filename when they make an
> | incompatible change to the API
>
> This seems to be the trend, but there's nothing in pkg-config's policies
> or best practices guide that specifies this. I'
]] Simon McVittie
| Upstreams are only meant to change the .pc filename when they make an
| incompatible change to the API - if XFCE 4 is still compatible with the API
| (but not necessarily the ABI) of the earliest version that had xfprint-1.0.pc,
| then it shouldn't be renamed.
This seems to b
On Fri, 19 Nov 2010 at 22:30:09 +0100, Dmitry Katsubo wrote:
> * Some libraries (e.g. GraphicsMagick) does not provide the list of
> libraries for statis linking via .pc (compare 'pkg-config --static
> --libs GraphicsMagick++' and 'GraphicsMagick++-config --libs'). Should
> it be fired as a bug for
Dmitry Katsubo writes:
> The first problem I faced is that it is difficult to explore what should
> be the list of libraries for static linking (as I have to provide the
> list of libraries which are direct dependencies as well as indirect). I
> know this problem is solved with libtool (which con
Dear Debian Developers!
In the application I am taking part in, I am trying to create a
configuration script to be able to provide two deliverables:
dynamically-linked executable and statically-linked.
The first problem I faced is that it is difficult to explore what should
be the list of librari
10 matches
Mail list logo
