how should .pc files be configured for "static only" builds?
lrn1986 at gmail.com
Wed May 21 10:02:02 PDT 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 21.05.2014 20:45, Roger Pack wrote:
> It's come to my attention the following conundrum:
> in my own words, it seems impossible to know if, when calling pkg-config,
> the library was compiled statically or dynamically" (so you don't know
> whether to call pkg-config --static or not).
> Has there been any improvement/progress on this as of late?
Shared builds are the default. Static linkage can be applied globally by
sprinkling everything with all kinds of --static* arguments. However, doing
static linking selectively can only be achieved by carefully arranging things
in the buildsystem.
Specifically, it means that you have to be the project developer, in which
case you can tweak the buildsystem in any way you want. Otherwise the amount
of patching required to achieve a specific static build can be overwhelming.
This is a symptom of poor support for user-controlled selective static builds
in autotools and libtool (which is fine by me, i've never been a fan of
static builds). It has nothing to do with pkg-config.
IMO, anyway. Also, i hope i've re-interpreted your question correctly.
O< ascii ribbon - stop html email! - www.asciiribbon.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
-----END PGP SIGNATURE-----
More information about the pkg-config