On Tue, 1 Aug 2006, [EMAIL PROTECTED] wrote:
So you would first check for the existence of pkg-config (and complain
if not there) and then use it to get the info needed.
and inevitably (since there's more than one version of pkg-config) start
to accumulate autoconf macros to filter through in
Hi all,
CPPUNIT provides an m4 macro AM_PATH_CPPUNIT which is in:
/usr/share/aclocal/cppunit.m4
Still, when I try to use AM_PATH_CPPUNIT in my configure.ac I get an
error. Shouldn't it find cppunit.m4 and use the macro? Or I need to
setup autoconf to find the macro?
Error:
configure.ac:13: erro
Am Tue, 1 Aug 2006 18:51:58 +0100
schrieb "Paulo J. Matos" <[EMAIL PROTECTED]>:
> Hi all,
>
> CPPUNIT provides an m4 macro AM_PATH_CPPUNIT which is in:
> /usr/share/aclocal/cppunit.m4
>
> Still, when I try to use AM_PATH_CPPUNIT in my configure.ac I get an
> error. Shouldn't it find cppunit.m4 a
On 01/08/06, Familie Porschberg <[EMAIL PROTECTED]> wrote:
In our project we have an autogen.sh script and call
"aclocal -I config/m4" there.
Under config/m4 there are all the m4 macros we are using.
Thanks a lot, indeed just calling aclocal did the trick. :-)
I seem to finally be entering th
Hi all,
Sometimes I wish to call configure with different flags. For example:
./configure CXXFLAGS="-ggdb -Wall -std=c++98"
or
./configure CXXFLAGS="-O3 -funroll-loops" --with-gmp
or some more like these. Having to be writing these all the time is
cumbersome and error-prone since for debugging
