Warnings-as-errors, /Wp64

  • Thread starter Thread starter Bern McCarty
  • Start date Start date
B

Bern McCarty

We have a large source base that we normally compile with /WX (treat all
warnings as errors) and /W3. I would like to add the /Wp64 switch to this
mix so that developers see the /Wp64 warnings but I don't want them to be
treated as errors. Treating them as errors would be impossible at this
point since there will be tons of them. At this point my aim is to build
awareness and at least get developers that are writing a lot of new code to
write it so that it is 64-bit clean.

Is there an easy way to do what I want to do?

-Bern
 
Hi Bern,

You want to mixed the /WX with the /Wp64, and exclude the /Wp64 warning
from the other warnings which treated as errors.

It seems... tough, I will consult this issue with the dev team member to
see is there a workaround for you to achieve that.


Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
 
Hi Bern,

Unfortunately, it appears impossible to exclude /Wp64 warnings from the /WX
warnings(errors).

However, one member of the dev team suggest:

"#pragma warning(error: ####)

where #### is replaced by the complete list of warnings that they care
about. Then, stop using /WX in the builds.

(Maybe you could extend #pragma warning (and the matching cmd line
switches) to allow specifying a warning level for an entire class of
warnings: #pragma warning(error: W1 W2 W3) for example...)
"


Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
 
Back
Top