Re: third party libaries

[Bob Friesenhahn]

On Thu, 3 Mar 2005, Johannes Drever wrote:

> On Thu, 3 Mar 2005, Bob Friesenhahn wrote:
> > If you are using Automake, you should express library dependencies via an 
> > LDADD statement (can be on a per-library level).  If the libraries are in 
> > the local build tree, the listed dependency should be the absolute or 
> > relative path to the library's uninstalled .la file.  If the libraries are 
> > already installed, then use -llib syntax.
> >
> > Automake will pass LDADD options to libtool "as is"
>
> I didn't want to make an application for each sublibrary. (i think LDADD is 
> for linking executabels?)

I use LDADD for both libraries and executables.

> As the libraries i want to use are already installed i should use the -llib 
> syntax, but where? i already passed the flags via AM_CPPFLAGS=... but is it 
> the right way? and how can i define one path to link at and une the location 
> in the makefile.am's ( or can i make autoconf search the path ?)

CPPFLAGS defines where to look for header files, not libraries.  You 
will need both.

There is also LIBS, which specifies a list of libraries to supply for 
all applications.  This is the common way to pass a list of libraries 
from autoconf to the Makefile.  You are not limited to using LIBS 
since you can add your own substitution variables, which supply 
additional options via a library-specific LDADD statement.

Use LDFLAGS to pass linker search path options from configure to the 
Makefile.

Bob
======================================
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/