Commit Graph

7 Commits

Author SHA1 Message Date
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 1bffea8aaf update installshield files; update version #s; fix Win custom action build 2018-07-17 12:42:39 -07: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 4a759ba246 Win build: include win_build in include directory list.
That way can include "config.h" in Win builds
2018-01-19 21:19:39 -08:00
Rom Walton c5bb4c4231 WINBUILD: Make the custom action project build again 2017-11-06 21:13:46 -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 8408b989cd WINBUILD: Since the installer custom actions now depend on libboinc and parts of it can be shared with other platforms, move it into a more neutral location. 2016-02-11 16:32:02 -05:00