You may need to share some specific error messages or a build log. Or, ideally, setup some kind of CI environment that mirrors your environment and reproduce your failure. Github has runners that have support for visual studio 2022 and I believe there are actions to install vcpkg. You could create a fork of the arrow repo, add a new CI job, reproduce the error, and then share the error with the mailing list. This will make it a lot easier for others to debug the root cause and opens up the possibility of later adding that as a regular nightly job.
On Fri, Mar 4, 2022 at 1:47 PM David Li <lidav...@apache.org> wrote: > > Not too sure but perhaps try a Release build, Debug builds have been a > problem for others, e.g. see ARROW-15298 [1] > > I've personally not gotten a debug build to work before. > > [1]: https://issues.apache.org/jira/browse/ARROW-15298 > > -David > > On Fri, Mar 4, 2022, at 17:55, Alex McRae (CW) wrote: > > Hi all, happy friday! > > I am having issues building arrow with flight and flightsql on a fresh > install of windows. > > My configuration uses VCPKG, static build, and visual studio 2022 generation. > The generation is successful however running cmake --build ./build --config > Debug fails. With a bunch of different errors stemming from winsock2.h, which > I understand comes from the Windows SDK, and resolve issues in the DLL. I > have attached a log below. > > I run these commands in the cpp/build directory of the arrow repository. As > outlined https://arrow.apache.org/docs/developers/cpp/windows.html > > cmake .. -DARROW_FLIGHT=ON -DARROW_FLIGHT_SQL=ON > -DCMAKE_TOOLCHAIN_FILE=C:/tools/vcpkg/scripts/buildsystems/vcpkg.cmake > -DARROW_DEPENDENCY_SOURCE=VCPKG -DARROW_BUILD_STATIC=ON > -DVCPKG_TARGET_TRIPLET=x64-windows-static -A x64 > -DARROW_DEPENDENCY_USE_SHARED=OFF > > cmake --build . --config Debug > > Let me know what you think, > > Alex McRae > > > Attachments: > > log.txt > >
