Commit Graph

4 Commits

Author SHA1 Message Date
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 1a33a39909 WINBUILD: Fix build breaks for debug builds 2013-10-24 01:05:14 -04:00
Rom Walton 7b73ef6dbf WINBUILD: Use correct calling convention for the vs2010 zlib libraries. 2013-10-17 17:17:38 -04:00
Rom Walton bcf8ca2565 WINBUILD: Update build environment to use Visual Studio 2010. 2013-10-17 15:27:03 -04:00