autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libraries transitives dependencies


From: Guillaume Rousse
Subject: libraries transitives dependencies
Date: Wed, 31 May 2006 10:38:45 +0200
User-agent: Thunderbird 1.5.0.2 (X11/20060425)

I often run into problem, when testing libraries presence, with
unresolved symbols. Unless misconprehension of mine, gcc don't force you
to solve all symbols at linking time when creating a shared libraries.
As a result, you have to add additional librairies in the linking
command, which is the purpose of the 5th argument of AC_CHECK_LIB.

However, the real problem here is that you have to know which exact
libraries you need to add. Unless the original one you're interested by
gives you a way to know them (pkgconfig, -config script, documentation),
it often turn into a painful search for what does provides the missing
symbols. It is even more painful if you didn't compiled it yourself,
which is the usual scenario when using linux distributions with
precompiled packages.

So my question is, what is the interest of such lazy symbol resolution ?
 Is it just a bad practice, or does it provide any kind of advantages ?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]