Maintaining header file directory structure on install

Pete Willemsen writes: > Hello. > > I'm struggling with figuring out a way to maintain my directory > structure for my header files. I have the following structure > >file1.c ... fileN.c PackageName/ Makefile.am configure.in ... > | >

Exporting variables

Hi all, To produce some documentation using doxygen, I have the following rule in my Makefile.am: doc : $(DOC_H_FILES) DEFINESDOC=`echo @DEFS@ | sed -e "y/-D/ /"` && \ export VERSION DEFINESDOC DOC_H_FILES && \ makeDoc && \ touch doc DOC_H_FILES is set in a file

AC_PATH_XTRA

Hi, On solaris, X11 needs some extra libs to be used. Apparently, AC_PATH_XTRA can find them and sets some variables: X_CFLAGS, X_LIBS, and X_EXTRA_LIBS. My question is what is the best way to use them? Is it: AC_PATH_XTRA LIBS=$LIBS $X_EXTRA_LIBS $X_LIBS TIA, Fred

Testing for a library with a function different from main() (Was: Testing for a library with $CXX (instead of $CC))

Alexandre Oliva writes: > On Apr 5, 2000, F Labrosse <[EMAIL PROTECTED]> wrote: > > > Is it possible to test for a library using $CXX instead of $CC? > > This is an `autoconf', not `automake', question. See the `Language > Choice' node in the a

Testing for a library with $CXX (instead of $CC)

Hi all, Is it possible to test for a library using $CXX instead of $CC? My problem is that on a Solaris box, some libraries won't link with cc while they do with CC (e.g. qt). Or is it better to set $CC to CC (instead of having $CC=cc and $CXX=CC). TIA, Fred