ARROW-11580 makes it straightforward to use vcpkg for dependencies. This has been well-tested with release builds, but there are some loose ends with debug builds. vcpkg installs debug libraries for the dependencies, but there are some problems linking them when -DCMAKE_BUILD_TYPE=DEBUG. I was able to get a debug build to succeed on Windows with VS 2019 by turning some features off
-DARROW_FLIGHT=OFF ^
-DARROW_GANDIVA=OFF ^
-DARROW_WITH_THRIFT=OFF ^
-DARROW_PARQUET=OFF ^
but there were linking errors when I turned any of those on. I think some of these errors can be resolved by setting additional \*\_MSVC\_\* prefix/suffix variables or by working around limitations of which dependencies vcpkg can and cannot install as dynamic link libraries.
I tested this after installing dynamic link libraries with vcpkg and with -DARROW_DEPENDENCY_USE_SHARED=ON. We should also test debug builds with static dependencies and on Linux and Mac.
Reporter: Ian Cook / @ianmcook
Related issues:
Note: This issue was originally created as ARROW-11796. Please see the migration documentation for further details.
ARROW-11580 makes it straightforward to use vcpkg for dependencies. This has been well-tested with release builds, but there are some loose ends with debug builds. vcpkg installs debug libraries for the dependencies, but there are some problems linking them when
-DCMAKE_BUILD_TYPE=DEBUG. I was able to get a debug build to succeed on Windows with VS 2019 by turning some features offbut there were linking errors when I turned any of those on. I think some of these errors can be resolved by setting additional
\*\_MSVC\_\*prefix/suffix variables or by working around limitations of which dependencies vcpkg can and cannot install as dynamic link libraries.I tested this after installing dynamic link libraries with vcpkg and with
-DARROW_DEPENDENCY_USE_SHARED=ON. We should also test debug builds with static dependencies and on Linux and Mac.Reporter: Ian Cook / @ianmcook
Related issues:
Note: This issue was originally created as ARROW-11796. Please see the migration documentation for further details.