Closed visr closed 2 months ago
Making those unique names based on xx.xx.xx versions is a source of problems (as the present case showed) and a waste. I find my disk full of DLL old versions in artifacts dir that never get removed. I've been building GDAL and PROJ for years with VS (to use in GMT) and I never changed the name of the DLL and also we never had a problem because of it. So, yes, please adopt a scheme where the DLL names change the least possible.
ping
Hi, I help to maintain a PROJ build for Julia, used in Proj.jl. These builds are cross compiled to the MinGW target, resulting into DLLs with the minor version in the name;
libproj_9_4.dll
. This is implemented in ProjVersion.cmake and ProjUtilities.cmake. With this DLL naming new GDAL builds are required for each minor PROJ release, also if they have the same SOVERSION.Looking at GDAL I get
libgdal-35.dll
, a suffix with the SOVERSION, implemented in https://github.com/OSGeo/gdal/pull/5701.Would such behavior also make sense for PROJ?