I didn't pay much attention to the CMake code. Now:
You don't need to deal with string(CONCAT ...). Normally you just need to
- treat VCPKG__FLAGS as CMake string (because this follows
CMAKE__FLAGS),
- treat as VCPKG_CMAKE_CONFIGURE_OPTIONS as CMake list, *quoting whole
list items* if needed.
David and Kai, thanks for your input. With Kai's hint I figured out that GDAL
was not being built with MrSID and ECW support because I didn't have the paths
right in my -DMRSID_INCLUDE_DIR, -DMRSID_LIBRARY, -DECW_INCLUDE_DIR and
-DECW_LIBRARY defines. This was causing the config step to fail. T
Michael,
I noticed you said the following:
"I am linking statically to GDAL built as a static library with vcpkg
(which builds without error)."
I may be interpreting this incorrectly, but it sounds like you intend to
link the NCSEcw library. However, I believe your ECW_LIBRARY variable
reference
IMO you ask for trouble when you manually inject -DFRMT_mrsid=ON into
CFLAGS and CXXFLAGS. This is CMake input ("ON"!). Let the configuration
do that for you. Did configuration successfully detect the dependency?
Check the config logs.
Kai
Am 22.02.25 um 05:15 schrieb Michael Katz via gdal-d
I am getting the following link errors when building my application in MSVC++:
1>gdal.lib(gdalallregister.cpp.obj) : error LNK2019: unresolved external symbol
_GDALRegister_ECW referenced in function
_GDALAllRegister@01>gdal.lib(gdalallregister.cpp.obj) : error LNK2019:
unresolved external symbo
