Re: [gdal-dev] GDAL DLL naming convention

2025-01-31 Thread Parveen Sharma via gdal-dev
Thanks for sharing this information From: David Klaus Sent: Friday, January 31, 2025 11:07 PM To: Parveen Sharma Cc: Michał Kowalczuk via gdal-dev Subject: Re: [gdal-dev] GDAL DLL naming convention Parveen, My company builds with vcpkg so this might not be

Re: [gdal-dev] GDAL DLL naming convention

2025-01-31 Thread Parveen Sharma via gdal-dev
Thanks so sharing this information. From: David Klaus Sent: Friday, January 31, 2025 11:07 PM To: Parveen Sharma Cc: Michał Kowalczuk via gdal-dev Subject: Re: [gdal-dev] GDAL DLL naming convention Parveen, My company builds with vcpkg so this might not be

Re: [gdal-dev] GDAL DLL naming convention

2025-01-31 Thread David Klaus via gdal-dev
Parveen, My company builds with vcpkg so this might not be applicable to you. But using the DGDAL_LIB_OUTPUT_NAME option I am able to specify the name of the output dll and lib file for our build. Here is how I set this option for our build: -DGDAL_LIB_OUTPUT_NAME=gdal3100 This worked for us for

[gdal-dev] GDAL DLL naming convention

2025-01-31 Thread Parveen Sharma via gdal-dev
Hello Were in past GDAL DLLs were named with version in them when built from source ? For e.g. gdal303.dll If yes, then is there any way to achieve the same now? Best regards, ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.or