[gdal-dev] Building GDAL with PROJ4 in a non-standard location?

Even Rouault even.rouault at spatialys.com
Thu Feb 16 07:51:55 PST 2017

On jeudi 16 février 2017 16:48:57 CET Emmanuel d'Angelo wrote:
> Hi everyone,
> I'm experimenting with a C++ package manager (conan.io for interested
> folks) to correctly setup my project and its dependencies.
> In this experiment, I'm trying to wrap GDAL and build GDAL 2.1.1 using a
> PROJ4 library that was put in a non-standard location by the package
> manager. When I had a look at the configure.in file, I could find an option
> to specify the path to PROJ4 install directory, but that is only set when
> using the option --with-static-proj4.
> Is there a way to pass the path to a dynamic library of PROJ4 when building


Yes, with that very same option. The "static" in --with-static-proj4 refers to a a static/dynamic 
linking done at build time rather than the default behaviour which is to use dlopen() / 
LoadLibrary() metchanisms at runtime.


Spatialys - Geospatial professional services
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20170216/155012a7/attachment-0001.html>

More information about the gdal-dev mailing list