Antw: Re: [asterisk-dev] How to bind extern include files or libs into * 1.4

[Tilghman Lesher]

On Sunday 22 April 2007, Brian Capouch wrote:
> Russell Bryant wrote:
> > 4) Set some information in the module itself to indicate that it depends
> > on the library.  In pbx_dundi, we have this special block:
> >
> > /*** MODULEINFO
> >     <depend>zlib</depend>
> >  ***/
> >
> > This tells the build system that pbx_dundi depends on zlib.  So,
> > menuselect will not let you select it if it is not found.  Also, the
> > Makefile will automatically include the information from ZLIB_INCLUDE
> > and ZLIB_LIB for building the module.
> >
> >
> > That should be everything.  There are some more complicated examples in
> > the tree.  For example, chan_zap can use libpri and libss7, but it does
> > not require it for it to be compiled and installed.  The build system
> > accounts for all of that.
>
> One last little mystery that would save me some manual hacking when I do
> my cross-compile builds:
>
> I am working on a couple of modules that require the CURL library.  I
> haven't quite figured out yet where the RHS of this line in makeopts
> originates:
>
> CURL_LIB=-L/usr/lib -lcurl -lidn -lz -lssl -lcrypto -ldl -lz
>
> In other words, who is in charge of figuring out those library
> dependencies?  I have grepped byself blue in the face through the
> sources and don't see just how that gets done.

It's the output of 'curl-config --libs'.

-- 
Tilghman