Re: [gdal-dev] On Internal PROJ When Building

Le 26/08/2021 à 18:33, Patrick Young a écrit : Thanks Even! As newer versions of Ubuntu pick up fresher versions of proj (was checking out https://packages.ubuntu.com/groovy/libproj-dev ), is there a minimum version of proj that'll be reasonabl

Re: [gdal-dev] On Internal PROJ When Building

Thanks Even! As newer versions of Ubuntu pick up fresher versions of proj (was checking out https://packages.ubuntu.com/groovy/libproj-dev), is there a minimum version of proj that'll be reasonable (e.g. 7 or 8) to use? P On Thu, Aug 26, 2021 at 9:44 AM Even Rouault wrote: > Actually looking

Re: [gdal-dev] On Internal PROJ When Building

Actually looking at the wiki page, I've just updated it since it would not have worked if the system PROJ is >= 6.0. The update consists in adding  -DPROJ_INTERNAL_CPP_NAMESPACE to CXXFLAGS when building PROJ so that C++ symbols of the "internal" proj don't clash with the ones of the system PRO

Re: [gdal-dev] On Internal PROJ When Building

Patrick, I guess this is at least relevant for the ubuntu-full config that uses libspatialite from the distro. This libspatialite must link against proj 6.3.1 from the Ubuntu 20.04 distro, whereas the GDAL we build will link against the PROJ built in the image, so without that trick, crashes

[gdal-dev] On Internal PROJ When Building

Hi, I was curious how relevant building an internal PROJ library is these days as described in this note https://trac.osgeo.org/gdal/wiki/BuildingOnUnixGDAL25dev I noticed GDAL's docker builds still do this. Are there some common dependencies that still use the older PROJ? Many thanks! Patrick