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 insert anything on configure
command line, because gdal-config will give the right path on every
system...
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 "#include <gdal.h>").
<path>/configure CPPFLAGS=-I/usr/include/gdal
How can I manage the two cases in the same configure.ac: system in which
gdal.h is in /usr/include and others in which it is in
/usr/local/include?
c.f. above. Leave passing include-paths to your users. Only he knows
(rsp. he is supposed to know) where a package's headers are installed.
A package's author can't know where his package's users may have
installed the package's headers into.
Ralf
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf
