This is a question about the DDK build environment. I am using the
latest Windows 7 driver kit.
In my sources file, I am using MSC_WARNING_LEVEL=/W4 /WX. The /WX part
of it makes the compiler treat warnings as errors.
However, the build tool won’t show me the warnings on the screen, so my
typical prompts will show something like:
error C2220: warning treated as error - no ‘object’ file generated
And that’s it. I would have to do type *.wrn to actually see what the
warnings were.
How do I make the build tool show warnings on screen?
Use /w (display warnings on screen):
http://msdn.microsoft.com/en-us/library/ms791595.aspx
On Sat, 07 Nov 2009 09:07:47 +0100, comrade wrote:
> This is a question about the DDK build environment. I am using the
> latest Windows 7 driver kit.
>
> In my sources file, I am using MSC_WARNING_LEVEL=/W4 /WX. The /WX part
> of it makes the compiler treat warnings as errors.
>
> However, the build tool won’t show me the warnings on the screen, so my
> typical prompts will show something like:
> error C2220: warning treated as error - no ‘object’ file generated
>
> And that’s it. I would have to do type *.wrn to actually see what the
> warnings were.
>
> How do I make the build tool show warnings on screen?
Thanks *slaps himself for not reading the documentation *
Cay Bremer wrote:
Use /w (display warnings on screen):
http://msdn.microsoft.com/en-us/library/ms791595.aspx
On Sat, 07 Nov 2009 09:07:47 +0100, comrade wrote:
>> This is a question about the DDK build environment. I am using the
>> latest Windows 7 driver kit.
>>
>> In my sources file, I am using MSC_WARNING_LEVEL=/W4 /WX. The /WX part
>> of it makes the compiler treat warnings as errors.
>>
>> However, the build tool won’t show me the warnings on the screen, so my
>> typical prompts will show something like:
>> error C2220: warning treated as error - no ‘object’ file generated
>>
>> And that’s it. I would have to do type *.wrn to actually see what the
>> warnings were.
>>
>> How do I make the build tool show warnings on screen?
>
Because I’m lazy when it comes to typing, I always go into my
\bin\generic.mac and change the “bcz” macro to include the W switch:
BCZ = build -cZMgW $*
That way I can always just bcz in the command window and get a clean build
that includes warnings in the output.
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“comrade” wrote in message news:xxxxx@ntdev…
> Thanks *slaps himself for not reading the documentation *
>
> Cay Bremer wrote:
>> Use /w (display warnings on screen):
>> http://msdn.microsoft.com/en-us/library/ms791595.aspx
>>
>>
>> - Cay
>>
>>
>> On Sat, 07 Nov 2009 09:07:47 +0100, comrade
>> wrote:
>>> This is a question about the DDK build environment. I am using the
>>> latest Windows 7 driver kit.
>>>
>>> In my sources file, I am using MSC_WARNING_LEVEL=/W4 /WX. The /WX part
>>> of it makes the compiler treat warnings as errors.
>>>
>>> However, the build tool won’t show me the warnings on the screen, so my
>>> typical prompts will show something like:
>>> error C2220: warning treated as error - no ‘object’ file generated
>>>
>>> And that’s it. I would have to do type *.wrn to actually see what the
>>> warnings were.
>>>
>>> How do I make the build tool show warnings on screen?
>>
>