madler
Add vc15 build files to contrib/vstudio.
I've added vc15 build fileles and tested the result with Visual Studio 2017 professional (Windows 10 and SDK 10.0.15063.0). Also I've added brebuild steps to zlibstat project (Release x64/Win32 configurations) to compile assembler files there.
Thanks
From: tbeu [mailto:[email protected]] Sent: Tuesday, August 15, 2017 12:27 PM To: madler/zlib [email protected] Cc: Dmitry Savelev [email protected]; Author [email protected] Subject: Re: [madler/zlib] Add vc15 build files to contrib/vstudio. (#270)
See also #243https://github.com/madler/zlib/pull/243.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/madler/zlib/pull/270#issuecomment-322396032, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOTWUdrZ6sDMLr5-i_ER9CTjwzxAlSkvks5sYUhBgaJpZM4OLmWl.
The project already has cmake support. Why would one check in static MSVC project files when you can have cmake generate them for you, for whichever version of Visual Studio that you have?
Why would one check in static MSVC project files when you can have cmake generate them for you, for whichever version of Visual Studio that you have?
To have all the nice features of static VS project files, e.g., multi-configuration, search, manual adaption of settings etc.
You can keep your search files around and regenerate project files from cmake. CMake creates multi-configuration projects.
It's good that you can also build configurations with CMake. But a VC project file can be built directly with MSBuild without even opening VS, no need to manually create configurations first, it can be opened in VS with all files nicely organized, it can be debugged more easily.
So why can't we just merge this? It won't prevent anyone from using CMake.
Author of this repo has been /afk for 2 years, so not sure anything's going to happen.
It's not correct, see the development in devel branch. But AFAIK contrib/ directory is not supported, see the README.
Well then @madler has the GitHub site configured incorrectly, as all the pull requests are targeting master and not develop.
@praiskup We don't want support, the files there work correctly. We'd just like to add one more build file for latest VS version...