That is what I guessed. But the documentation says: CURL_LIBRARY_RELEASE•<https://gdal.org/development/building_from_source.html#cmdoption-arg-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 link with the dynamic library by default or I need to set CURL_USE_STATIC_LIBS=OFF explicitly?
Thanks! From: Even Rouault <even.roua...@spatialys.com> Date: Saturday, March 2, 2024 at 1:08 PM To: Fengting Chen <fengting.c...@oracle.com>, gdal-dev@lists.osgeo.org <gdal-dev@lists.osgeo.org> Subject: Re: [External] : Re: [gdal-dev] 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<https://urldefense.com/v3/__http:/www.spatialys.com__;!!ACWV5N9M2RV99hQ!JLgqR0Xmpy0AUkdrzdfKyclw3MYEvcOPpYdP04m-uxbTA0uf-YWzEltfLKASB4MXKlj9dC0VOJFC_d3zpeRnm3HTUWIn$> My software is free, but my time generally not.
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
