Oops, I hadn't inferred that. Thanks Even!
Emmanuel [image: Pix4D] <http://pix4d.com/> Emmanuel d'Angelo | Model Team Technical Lead EPFL Innovation Park *| Building F | *1015 Lausanne, Switzerland t. +41 21 552 05 96 *https://pix4d.com <https://pix4d.com/> | * *[email protected] <[email protected]>* *[image: Twitter] <https://twitter.com/pix4d>[image: Facebook] <https://www.facebook.com/Pix4D/>[image: LinkedIn] <https://www.linkedin.com/company/pix4d>[image: YouTube] <https://www.youtube.com/channel/UCXHBqjCbv1wj_-itfvpVNIA?sub_confirmation=1>* 2017-02-16 16:51 GMT+01:00 Even Rouault <[email protected]>: > 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 > > > GDAL? > > > > Emmanuel, > > > > 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. > > > > Even > > > > -- > > Spatialys - Geospatial professional services > > http://www.spatialys.com >
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
