Re: [gdal-dev] [External] : Re: GDAL build on windows failed for FILEGDB driver

Le 02/03/2024 à 21:14, Fengting Chen a écrit : Thanks, that is clear now. One more question, anywhere to get proj_9_3.lib and sqlite3 .lib, most downloadable package only has .dll. conda or vcpkg. cf https://gdal.org/download.html#windows *From: *Even Rouault *Date: *Saturday, March 2,

Re: [gdal-dev] [External] : Re: GDAL build on windows failed for FILEGDB driver

Thanks, that is clear now. One more question, anywhere to get proj_9_3.lib and sqlite3 .lib, most downloadable package only has .dll. From: Even Rouault Date: Saturday, March 2, 2024 at 1:50 PM To: Fengting Chen , gdal-dev@lists.osgeo.org Subject: Re: [External] : Re: [gdal-dev] GDAL build on

Re: [gdal-dev] [External] : Re: GDAL build on windows failed for FILEGDB driver

That is what I guessed. But the documentation says: CURL_LIBRARY_RELEASE• Path to a shared or static library file, such as libcurl.dll, libcurl.so, libcurl.lib, or other name. If I use .lib here, will GDAL

Re: [gdal-dev] [External] : Re: GDAL build on windows failed for FILEGDB driver

Le 02/03/2024 à 19:36, Fengting Chen a écrit : That is what I guessed. But the documentation says: CURL_LIBRARY_RELEASEÁ Path to a shared or static library file, such as libcurl.dll, libcurl.so, lib

Re: [gdal-dev] [External] : Re: GDAL build on windows failed for FILEGDB driver

set (CURL_LIBRARY_RELEASE "E:/SDK/curl-8.6.0_1-win64-mingw/bin/libcurl-x64.dll" CACHE FILEPATH "" FORCE) ==> XXX_LIBRARY[_RELEASE/_DEBUG] should point to a .lib import library, not to the .dll directly -- http://www.spatialys.com My software is free, but my time generally not. _

Re: [gdal-dev] [External] : Re: GDAL build on windows failed for FILEGDB driver

Thanks, removing ‘+’ helped. But the next error is the link error: E:\SDK\curl-8.6.0_1-win64-mingw\bin\libcurl-x64.dll : fatal error LNK1107: invalid or corrupt file: cannot read at 0x2C0 [E:\gdal-3.8.4\build\GDAL.vcxproj] The cmake option is: set (GDAL_USE_CURLON CACHE BOOL

Re: [gdal-dev] gdalinfo and WMT_MS_Capabilities: how to get Dimension and its Extent?

Andrea, if I run "gdalinfo -json WMSURL -sd 1", I can read a lot of info about it, but I do not see Dimension and its Extent in the json output (below an example from WMS request). default="2024-03-01T00:00:00Z">2024-01-01T00:00:00.000Z,2024-01-02T00:00:00.000Z,2024-01-03T00:00:00.000Z,2024-0

[gdal-dev] gdalinfo and WMT_MS_Capabilities: how to get Dimension and its Extent?

Hi, if I run "gdalinfo -json WMSURL -sd 1", I can read a lot of info about it, but I do not see Dimension and its Extent in the json output (below an example from WMS request). 2024-01-01T00:00:00.000Z,2024-01-02T00:00:00.000Z,2024-01-03T00:00:00.000Z,2024-01-04T00:00:00.000Z I would like to hav