Fix Visual Studio Warning Level Error: Difference between revisions
Jump to navigation
Jump to search
Note:I will write this article later, please don't delete it
GamerDude27 (talk | contribs) mNo edit summary |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
I will write this article later, please don't delete it | {{note|I will write this article later, please don't delete it}} | ||
==What is it?== | ==What is it?== | ||
If your warning level is set too high when building Source 2013 SDK under Visual Studio 2013, some negligible errors will be taken seriously by the compiler. | |||
Visual | These errors can be ignored, but Visual Studio doesn't think so. | ||
Although | |||
If your warning level is set to '''Level 3 (/W3)''', which is the default, Visual Studio will not let [[VPC]] continue to generate '''client.dll''' or '''server.dll''' when building. | |||
Although all the '''.obj''' files in the project will be generated, the compiler will still not call [[VPC]] to generate the final files we want because it thinks these errors are serious and cannot be ignored. | |||
Microsoft has also published articles explaining this. Please click this link to visit the official Microsoft article [[https://docs.microsoft.com/en-us/cpp/error-messages/compiler-warnings/compiler-warning-level-3-c4800?view=vs-2015 Compiler Warning (level 3) C4800]] | |||
Latest revision as of 17:06, 25 July 2020
Note:I will write this article later, please don't delete itWhat is it?
If your warning level is set too high when building Source 2013 SDK under Visual Studio 2013, some negligible errors will be taken seriously by the compiler.
These errors can be ignored, but Visual Studio doesn't think so.
If your warning level is set to Level 3 (/W3), which is the default, Visual Studio will not let VPC continue to generate client.dll or server.dll when building.
Although all the .obj files in the project will be generated, the compiler will still not call VPC to generate the final files we want because it thinks these errors are serious and cannot be ignored.
Microsoft has also published articles explaining this. Please click this link to visit the official Microsoft article [Compiler Warning (level 3) C4800]