bug-gnulib
[Top][All Lists]
Advanced

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

Re: The havelib module


From: Sylvain Beucler
Subject: Re: The havelib module
Date: Fri, 6 Feb 2009 23:16:33 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

On Mon, Feb 02, 2009 at 09:18:14PM +0100, Simon Josefsson wrote:
> Sylvain Beucler <address@hidden> writes:
> 
> > Hi,
> >
> > I'm trying to implement simply a '--with-mylib=/path/to/mylib' option
> > in 'configure', and I'm wondering if the 'havelib' would help.
> 
> Hi.  I believe it does.
> 
> > However I don't really understand how it's meant to be
> > used. Apparently its m4 macros need to be used within a macro
> > definition?
> >
> > Can you explain me basically what it does and how to use it?
> > (is it even meant for external use?)
> 
> I'm using it in some projects which aren't using gnulib otherwise, such
> as for example libssh2:
> 
> http://www.libssh2.org/wiki/index.php/Main_Page
> http://libssh2.cvs.sourceforge.net/viewvc/libssh2/libssh2/
> 
> Typically you add the lib-ld.m4, lib-link.m4, and lib-prefix.m4 macros
> to your project's m4/ directory, and add something like this to
> configure.ac:
> 
>   AC_LIB_HAVE_LINKFLAGS([ssl], [crypto], [#include <openssl/ssl.h>])
> ...
>   AC_LIB_HAVE_LINKFLAGS([gcrypt], [], [#include <gcrypt.h>])
> ...
>   AC_LIB_HAVE_LINKFLAGS([z], [], [#include <zlib.h>])
> 
> Then add to *_LDFLAGS the automake variables, e.g.:
> 
> libssh2_la_LDFLAGS = $(VERSION) -no-undefined \
>       $(LTLIBGCRYPT) $(LTLIBSSL) $(LTLIBZ)
> 
> See complete usage in:
> 
> http://libssh2.cvs.sourceforge.net/viewvc/libssh2/libssh2/configure.in?revision=1.63&view=markup
> http://libssh2.cvs.sourceforge.net/viewvc/libssh2/libssh2/src/Makefile.am?revision=1.13&view=markup
> 
> Of course, you may use gnulib-tool to import the files too, to avoid
> manual work.  But the files are relatively stable and have been tested
> on many platforms already.
> 
> Read the *.m4 files, they contain documentation for the various macros
> you may use.

Thanks, I just couldn't find the main macro to call, and your examples
are good.


The AC_LIB_HAVE_LINKFLAGS macro generates options like
"--with-libmylib-prefix".

It sounds a bit unclear to specify options such as
--without-libmylib-prefix to disable "mylib" (i.e. it sounds like
we're disabling mylib's *additional prefix* only, "--without-mylib"
would be more straightforward).

Is that normal?

-- 
Sylvain




reply via email to

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