6 Commits

Author	SHA1	Message	Date
Vitalii Koshura	d5026075c0	[windows] simplify *.vcxproj files by removing duplicates and moving the most of the common properties to the imported boinc.props and pch.props files ... Signed-off-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>	2024-09-15 03:08:29 +02:00
Vitalii Koshura	b3c4a6983f	[Windows] Retarget solution to VS2022 ... Get rid of all old solutions and projects. Switch to CUDA 12.0.0. Add crypt_proj to the solution. Use 'windows-2022' on CI. This fixes #4917. Signed-off-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>	2022-12-29 20:46:33 +01:00
David Anderson	05e3ad68b9	Make 32-bit builds work again by massive editing of project files.	2018-01-25 02:02:05 -08:00
David Anderson	159ef61f21	Update project files to work for Release mode also	2018-01-25 01:16:42 -08:00
David Anderson	ca80cac75a	Win build: manage compiler warnings better: ... VS lets you choose the compiler warning level, 0 to 4. Higher is good because compiler warnings often indicate bugs. However, some warnings are noise, and having a lot of them is bad because they conceal the important ones. As an example, a recent update to VS2010 causes it to spew warnings of the form "function _strdup() is deprecated; use _strdup() instead. So the new policy is: - everything compiles with warning level 4 - in boinc_win.h we use #pragmas to suppress 3 specific warnings that occur a lot in our code, and are not bugs: - the _function names as described above - constant conditional expression (like while(1)) - conversion from int to char And the goal is to build everything with zero warnings except from outside code like zip. We're pretty close to that. The project files for other VS versions should be modified to also use level 4 everywhere.	2017-01-27 01:27:32 -08:00
Rom Walton	bcf8ca2565	WINBUILD: Update build environment to use Visual Studio 2010.	2013-10-17 15:27:03 -04:00