On Mon, 2007-07-16 at 20:43 +0200, Benoit SIGOURE wrote: > Hello Joao Miguel, > Hello Benoit, ... .. . > 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 clear now. > > 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 ?? 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 to support the option you suggest ? Can you point me to good documentation on these "directives" ? for both configure.ac and Makefile.am... Thank you :) jmf > > Cheers, > > _______________________________________________ > Autoconf mailing list > Autoconf@xxxxxxx > http://lists.gnu.org/mailman/listinfo/autoconf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
