Ralf Wildenhues wrote:
* Lorenzo Bettini wrote on Sun, May 17, 2009 at 09:01:18PM CEST:
Ralf Wildenhues wrote:
* Lorenzo Bettini wrote on Sun, May 17, 2009 at 12:27:32PM CEST:
Ralf Wildenhues wrote:
You can just use pkg-config --static all the time, unless
( disable_static && ( host_os == Linux || host_os == Solaris ) )
Works wonders! :-)
mhhh... so basically this means that it is better not to use
Libs.private in the pkg-config file,
No, that is not what I said. Doing that will continue to do the wrong
thing even when Libtool is fixed one day.
No, I meant: not using Libs.private at all is however a safe choice,
isn't it?
No, it isn't. At least that's how I understand it. Why would you think
so?
Only on GNU/Linux and Solaris it might be safe, and only if you don't
care about static linkage.
No I meant: if additional libraries are shown when building with shared
library enable, this should do no harm, shouldn't it?
In such case, one could simply not use .Private specification in .pc file.
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net
