Build just doesn't work on windows with MSVC 2017. Any chance to put together decent .vcproj files?
- Dominant language
- C++
- Stars
- 17.1k
- Forks
- 4.3k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 88
Description
Hey guys, would you accept a few decent .vcproj files to build on windows?
What you have with all these cmake and vcpkg is
a. overly complicated
b. doesn't work
and the worst of it, with .vcproj it's sorta easy to figure out what needs to be tweaked, like external library support ( it wouldn't hurt to list those out ) and replaceable #(pound)define directives.
Can we agree to some conditions of peace?
I will have PR by next Sunday EOD.
Contributor guide
Research direction
Start by reviewing the existing CMake and vcpkg build setup and identify the external libraries and replaceable preprocessor definitions that the issue says should be represented. Done means providing usable .vcproj files that build Apache Arrow on Windows with MSVC 2017 and make those dependencies and definitions clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100