On Jul 16, 2007, at 10:01 PM, Joao Miguel Ferreira wrote:
On Mon, 2007-07-16 at 20:43 +0200, Benoit SIGOURE wrote:Hello Joao Miguel,Hello Benoit,
:D
Well, I don't see why it should work. Maybe some Linux distros chose to put /usr/local/include in the default include path of their compiler, but I don't think this is mandatory. Moreover, your library is not necessarily installed under /usr/local (think of a user that ./configure your package with --prefix=$HOME/local).You're right again... I was seeing this the wrong way :). Its more clearnow.The usual way to deal with this is to add a --with-libfoo=PATH option to your configure script that users will use to tell where libfoo has been installed. If they don't provide a --with-libfoo argument, you can assume that they expect to find libfoo in their compiler's standard include and lib directories.and that would be /usr/include and /usr/lib ??? Is there a universal approach for this... some kind of Autotools best practices ??
No universal approach but you can easily provide a --with-libfoo switch as I said.
I'm using Autotools only by changing Makefile.am and configure.ac...Which of these files do I change in order for the ./configure script tosupport the option you suggest ?Can you point me to good documentation on these "directives" ? for bothconfigure.ac and Makefile.am... Thank you :)
Alright so since the --with-libfoo option is a ./configure option, it seems logical to have something to add in configure.ac to add it. :)
Have a look at this page:http://www.gnu.org/software/autoconf/manual/html_node/External- Software.html
It has a couple of good examples that kinda do what you need. Cheers, -- Benoit Sigoure aka Tsuna EPITA Research and Development Laboratory
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
