[gdal-dev] GDAL and proj dll name.

Joaquim Manuel Freire Luís jluis at ualg.pt
Wed Jan 22 11:40:01 PST 2020

FYI, this is what I do with my build. Since I want to control the DLL name I’ve added  this lines to  src\ lib_proj.cmake

# If a renaming of the proj dll has been set in ConfigUser.cmake

and in a ConfigUser.cmake file (included in the main CMakeLists.txt file) I have

set (PROJ4_DLL_RENAME proj_w${BITAGE})

where BITAGE is either 32 or 64.

If there is interest for such a solution I could make a PR for it


From: gdal-dev <gdal-dev-bounces at lists.osgeo.org> On Behalf Of Tamas Szekeres
Sent: Wednesday, January 22, 2020 3:49 PM
To: Even Rouault <even.rouault at spatialys.com>
Cc: gdal-dev <gdal-dev at lists.osgeo.org>
Subject: Re: [gdal-dev] GDAL and proj dll name.

Hi Even,

Thank you, I've not considered to modify the linking behavior of proj.dll at this stage, but as far as it solves the problem I'm fine with it.

Best regards,


Even Rouault <even.rouault at spatialys.com<mailto:even.rouault at spatialys.com>> ezt írta (időpont: 2020. jan. 22., Sze, 15:01):
Hi Tamas,

> However the GDAL build (like for
> https://github.com/OSGeo/gdal/blob/v2.4.4/gdal/ogr/ogrct.cpp) still using
> the default proj.dll name which cannot be configured in the opt file.

It can. You need to define -DPROJ_STATIC for that. -DPROJ_STATIC is a bit
confusing. It didn't mean a static build, but something that was linked at
build time (either a static or dynamic lib), to be opposed at being loaded at
runtime with LoadLibrary(). That's what you want to use.

# PROJ stuff
# Uncomment the following lines to link PROJ library statically. Otherwise
# it will be linked dynamically during runtime.
# To use the new API of proj5 or later, use
# for proj 4.x:

#PROJ_INCLUDE = -Id:\projects\proj.4\src
#PROJ_LIBRARY = d:\projects\proj.4\src\proj_i.lib


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

More information about the gdal-dev mailing list