Dear autoconf users/developers,
I have the following question concerning the use of special characters
in variables. After reading the documentation chapter [1], I've come to
the conclusion, that I cannot define the following in configure.ac:
CXXFLAGS="-D__int64=\"long long\" ${CXXFLAGS}"
AC_CHEC
I have this configure.ac file:
AC_PREREQ([2.67])
AC_INIT([myapp], [0.2], [cand...@meeo.it])
AM_INIT_AUTOMAKE([-Wall -Werror foreign])
LT_PREREQ([2.2])
LT_INIT([dlopen])
AC_CONFIG_SRCDIR([src/ESM.cpp])
AC_CONFIG_HEADERS([config.h])
AC_DEFINE([ESM_VERSION], ["1.3.2"], [Soil Mapper version])
AC_DEFI
On 10/18/2011 04:26 PM, Alessandro Candini wrote:
Before upgrading my Ubuntu linux to 11.10 version, I had gdal.h under
/usr/local/include: configure and make succeed without errors.
Now I have it under /usr/include/gdal and I get that gdal.h cannot be
found (in my source files there is a simple
I see.
But gdal have a nice executable called gdal-config, similar to pkg-config:
user@host ~ $ gdal-config --cflags
-I/usr/include/gdal
user@host ~ $ gdal-config --libs
-L/usr/lib -lgdal1.7.0
Is there a way to use it like I do with PKG_CHECK_MODULES?
In this way I could avoid the user to inser
On 2011-10-18 15:57 +0200, Dmitry Katsubo wrote:
> I have the following question concerning the use of special characters
> in variables. After reading the documentation chapter [1], I've come to
> the conclusion, that I cannot define the following in configure.ac:
>
> CXXFLAGS="-D__int64=\"long l
On 10/18/11 06:57, Dmitry Katsubo wrote:
> CXXFLAGS="-D__int64=\"long long\" ${CXXFLAGS}"
This appears to be more of a shell question than an autoconf
question. From an autoconf point of view, you probably shouldn't
be messing with CXXFLAGS -- that's a variable that the
user should be setting.
>
On 18.10.2011 17:21, Nick Bowler wrote:
> A possible solution in this case is to just use AC_DEFINE:
>
> AC_DEFINE([__int64], [long long], [description if you use autoheader])
> AC_CHECK_HEADER([jni.h])
>
> Autoconf will take care of including the definition in subsequent
> configure tests. I
On 10/18/11 12:06, Dmitry Katsubo wrote:
> From this I conclude (maybe I am wrong) that
> autoconf does not pipe this string to shell (that will do the correct
> string / argument expansion), but somehow tries to execute compiler
> going the primitive split of arguments by spaces (as you have shown
On 18 October 2011 18:14, Alessandro Candini wrote:
> I see.
>
> But gdal have a nice executable called gdal-config, similar to pkg-config:
> user@host ~ $ gdal-config --cflags
> -I/usr/include/gdal
> user@host ~ $ gdal-config --libs
> -L/usr/lib -lgdal1.7.0
>
> Is there a way to use it like I do
