MironAtHome edited a comment on issue #12114: URL: https://github.com/apache/arrow/issues/12114#issuecomment-1009265400
``` My understanding is that some effort done to maintain single set of scripts and use parameters to drive features / files selected for compiler to build product. I will try to emulate it closely. For the moment I already have vcproj project file for Visual Studio 2017 ( I believe it will work with editions 2019 and 2022 as well ) that builds parquet library. Need to a. document dependencies or confirm those are submodules b. wire in parameters driving similar to cmake feature / file filtering c. take a step back and consider placeholders, replaced by cmake d. ensure and run unit tests --- optionally / next on the list e. add c# wrappers to some of the code using c++ CLR to provide for seamless integration with .NET f. replace getenv with updated / secure version getenv_s for test feature ---- The advantage of having vcproj files is that anyone with Visual Studio will be able to load those, clone dependencies ( unless I missed those are submodules that just need a sync up? ) and run build. And if something fails it would be fairly transparent how and what needs to be fixed. Learning new tools, such as CMake is probably great, but it does take time. So, having vcproj is really nice to get up and running quickly. ** ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
