On mercredi 6 mai 2020 18:17:34 CEST Craig Delancy wrote: > Windows 10, 64-bit > > I'm having a bit of trouble building GDAL from source. > It seems like it has a problem linking to PROJ, which build without issue > for me. Is anyone here familiar with this specific error? > > 1> Creating library gdal_i.lib and object gdal_i.exp > 1>proj.lib(filemanager.obj) : error LNK2019: unresolved external symbol > __imp_SHGetFolderPathW referenced in function > proj_context_get_user_writable_directory
Is it a static build of PROJ ? Which PROJ version ? According to https://docs.microsoft.com/en-us/windows/win32/api/shlobj_core/nf-shlobj_core-shgetfolderpathw SHGetFolderPathW() is defined in Shell32.lib, so perhaps adding shell32.lib to the nmake.opt's PROJ_LIBRARY variable will help. I'm a bit puzzled why that wouldn't trigger in PROJ AppVeyor static builds though. I see in https://ci.appveyor.com/api/buildjobs/xtgh93qbh7u96l5x/log that they have shell32.lib in linking lines. But perhaps that one comes from one of the dependent library like curl. Are you doing a non-curl enabled PROJ build ? But in that case, the linking of PROJ binaries would likely fail too. Hum... -- Spatialys - Geospatial professional services http://www.spatialys.com
_______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
