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_CURL ON CACHE BOOL "" FORCE) set (CURL_INCLUDE_DIR "E:/SDK/curl-8.6.0_1-win64-mingw/include" CACHE PATH "" FORCE) set (CURL_LIBRARY_RELEASE "E:/SDK/curl-8.6.0_1-win64-mingw/bin/libcurl-x64.dll" CACHE FILEPATH "" FORCE) Any idea? From: Even Rouault <even.roua...@spatialys.com> Date: Friday, March 1, 2024 at 5:54 PM To: Fengting Chen <fengting.c...@oracle.com>, gdal-dev@lists.osgeo.org <gdal-dev@lists.osgeo.org> Subject: [External] : Re: [gdal-dev] GDAL build on windows failed for FILEGDB driver Le 01/03/2024 à 20:31, Fengting Chen via gdal-dev a écrit : Hi, I am using VS2015 terminal and cmake to build GDAL on windows. I got the following compilation error for filegdbindex_write.cpp. Any idea? I kind of remember there was a ticket about that (probably closed). Basically VS2015 has incomplete C++11 support. You might go over that issue by replace the +[] lambda pattern with just [] I believe. But you'd better upgrade your compiler. The 3.9 branch requires C++17 support, which requires VS2017 -- http://www.spatialys.com<https://urldefense.com/v3/__http:/www.spatialys.com__;!!ACWV5N9M2RV99hQ!N7D9wGetkwWAVmRFBxeY1vj2M5dCjlmEJYIu4L8eVIiyJGITK8KWuYu9jFqHfduaiEuEc8PCCTOJ51txLyg4nXpErfxk$> 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
