I build the code with WDK build environment WinXP Check. and that shows there is a build warning.but while i check the build log “buildchk_wxp_x86.log” ,there is no any warning message.and checking with OACR(Microsoft Auto Code Review). there is no warning message either. how can i get this warning message ?
Log :
OACR monitor running already
D:\usbdriver>build -ceZ
path contains nonexistant c:\program files\common files\lenovo, removing
BUILD: Compile and Link for x86
BUILD: Start time: Mon Mar 14 14:08:17 2011
BUILD: Examining d:\usbdriver directory for files to compile.
d:\usbdriver Auto-cleaning queue for ‘roo
t:x86chk’ (10 of 10 file(s) removed)
Invalidating OACR warning log for ‘root:x86chk’
BUILD: Compiling and Linking d:\usbdriver directory
Configuring OACR for ‘root:x86chk’ - _NT_TARGET_VERSION SET TO WINXP Compiling resources - usb.rc Compiling - read.c Compiling - write.c Compiling - ioctl.c Compiling - log.c Compiling - purge.c Compiling - mask.c Compiling - generating code… Linking Executable - objchk_wxp_x86\i386\usbdriver.sys BUILD: Finish time: Mon Mar 14 14:08:21 2011 BUILD: Done
-----Original Message-----
From: xxxxx@hotmail.com
Sent: Monday, March 14, 2011 2:29 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] A short question with WDK build.
Hi all,
I build the code with WDK build environment WinXP Check. and that shows there is a build warning.but while i check the build log “buildchk_wxp_x86.log” ,there is no any warning message.and checking with OACR(Microsoft Auto Code Review). there is no warning message either. how can i get this warning message ?
Log :
OACR monitor running already
D:\usbdriver>build -ceZ
path contains nonexistant c:\program files\common files\lenovo, removing
BUILD: Compile and Link for x86
BUILD: Start time: Mon Mar 14 14:08:17 2011
BUILD: Examining d:\usbdriver directory for files to compile.
d:\usbdriver Auto-cleaning queue for ‘roo
t:x86chk’ (10 of 10 file(s) removed)
Invalidating OACR warning log for ‘root:x86chk’
BUILD: Compiling and Linking d:\usbdriver directory
Configuring OACR for ‘root:x86chk’ - _NT_TARGET_VERSION SET TO WINXP Compiling resources - usb.rc Compiling - read.c Compiling - write.c Compiling - ioctl.c Compiling - log.c Compiling - purge.c Compiling - mask.c Compiling - generating code… Linking Executable - objchk_wxp_x86\i386\usbdriver.sys BUILD: Finish time: Mon Mar 14 14:08:21 2011 BUILD: Done
Don’t know if the warnings appear in the .log file since I usually
look in the .wrn file, try that. Also you can specify the /w switch
which will display warnings on the screen.
Cheers
/Faik
On Mon, Mar 14, 2011 at 10:29 AM, wrote: > Hi all, > > I build the code with WDK build environment WinXP Check. and that shows there is a build warning.but while i check the ?build log “buildchk_wxp_x86.log” ,there is no any warning message.and checking with OACR(Microsoft Auto Code Review). there is no warning message either. ?how can i get this warning message ? > > Log : > > OACR monitor running already > D:\usbdriver>build -ceZ > path contains nonexistant c:\program files\common files\lenovo, removing > BUILD: Compile and Link for x86 > BUILD: Start time: Mon Mar 14 14:08:17 2011 > BUILD: Examining d:\usbdriver directory for files to compile. > ? ?d:\usbdriver Auto-cleaning queue for ‘roo > t:x86chk’ (10 of 10 file(s) removed) > Invalidating OACR warning log for ‘root:x86chk’ > BUILD: Compiling and Linking d:\usbdriver directory > Configuring OACR for ‘root:x86chk’ - > _NT_TARGET_VERSION SET TO WINXP > Compiling resources - usb.rc > Compiling - read.c > Compiling - write.c > Compiling - ioctl.c > Compiling - log.c > Compiling - purge.c > Compiling - mask.c > Compiling - generating code… > Linking Executable - objchk_wxp_x86\i386\usbdriver.sys > BUILD: Finish time: Mon Mar 14 14:08:21 2011 > BUILD: Done > > ? ?9 files compiled - 1 Warning > ? ?1 executable built > > D:\usbdriver> > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer >
Or promote warnings to errors. (/WX). I prefer that setting. It gets
rid of the warnings.
Mark Roddy
On Mon, Mar 14, 2011 at 6:04 AM, Faik Riza wrote: > Don’t know if the warnings appear in the .log file since I usually > look in the .wrn file, try that. Also you can specify the /w switch > which will display warnings on the screen. > > Cheers > /Faik > > On Mon, Mar 14, 2011 at 10:29 AM, ? wrote: >> Hi all, >> >> I build the code with WDK build environment WinXP Check. and that shows there is a build warning.but while i check the ?build log “buildchk_wxp_x86.log” ,there is no any warning message.and checking with OACR(Microsoft Auto Code Review). there is no warning message either. ?how can i get this warning message ? >> >> Log : >> >> OACR monitor running already >> D:\usbdriver>build -ceZ >> path contains nonexistant c:\program files\common files\lenovo, removing >> BUILD: Compile and Link for x86 >> BUILD: Start time: Mon Mar 14 14:08:17 2011 >> BUILD: Examining d:\usbdriver directory for files to compile. >> ? ?d:\usbdriver Auto-cleaning queue for ‘roo >> t:x86chk’ (10 of 10 file(s) removed) >> Invalidating OACR warning log for ‘root:x86chk’ >> BUILD: Compiling and Linking d:\usbdriver directory >> Configuring OACR for ‘root:x86chk’ - >> _NT_TARGET_VERSION SET TO WINXP >> Compiling resources - usb.rc >> Compiling - read.c >> Compiling - write.c >> Compiling - ioctl.c >> Compiling - log.c >> Compiling - purge.c >> Compiling - mask.c >> Compiling - generating code… >> Linking Executable - objchk_wxp_x86\i386\usbdriver.sys >> BUILD: Finish time: Mon Mar 14 14:08:21 2011 >> BUILD: Done >> >> ? ?9 files compiled - 1 Warning >> ? ?1 executable built >> >> D:\usbdriver> >> >> — >> NTDEV is sponsored by OSR >> >> For our schedule of WDF, WDM, debugging and other seminars visit: >> http://www.osr.com/seminars >> >> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer >> > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer >
i didn’t find the wrn file ,err file , would the “build -ceZ” command generate that ? the build /help say that the -e parameter will generate that files. i did set MSC_WARNING_LEVEL=/W3 in the source file.
If that is in fact the cause, you can either remove the offender from your
path, or add ‘i’ to your build command:
Build -ceiZ
This is one of the dumbest diagnostic messages EVAH.
Good luck,
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Monday, March 14, 2011 10:19 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] A short question with WDK build.
Thank you!
Something must be missed!!
i didn’t find the wrn file ,err file , would the “build -ceZ” command
generate that ? the build /help say that the -e parameter will generate that
files. i did set MSC_WARNING_LEVEL=/W3 in the source file.
The command “Build -ceiZ” work with the same result. no wrn file and no err file.
and below is show
9 files compiled - 1 Warning
1 executable built
and it is real no such “c:\program files\common files\lenovo” path in my system.
Of course it does not exist – that’s exactly what the error message was
telling you. The point is that your PATH variable contains that path.
It may be a leftover from the day you purchased your computer, or
perhaps you installed something and later removed it. However it got
there, it IS in your PATH. If you go remove it, the warning will go
away. I just tried this to confirm it.
You get to the environment variables through the System control panel,
Advanced, Environment Variables. Check both the User variables and the
System variables. (And pressing the Windows key with Pause/Break is a
quick way to bring up the System control panel.)
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
I have remove the path from environment variables .
but my question is why i use the -e parameter to build the code ,but it doesn’t generate WRN file and ERR file ? is there any settings to prevent the parameters from taking effect ?
I have remove the path from environment variables .
but my question is why i use the -e parameter to build the code ,but it doesn’t generate WRN file and ERR file ? is there any settings to prevent the parameters from taking effect ?
The warning you got was not “that sort of warning”. Build only creates
the .wrn file if there are warnings, and the .err file if there are
errors. There are a few warnings and errors around the edge of the
build, such as the one you saw, which get counted in the summary on the
screen at the end but which don’t go into the .wrn or .err files.
Try putting a change in a source file so the compiler reports warnings
or errors, and you should then see the files.
I have remove the path from environment variables .
but my question is why i use the -e parameter to build the code ,but it doesn’t generate WRN file and ERR file ? is there any settings to prevent the parameters from taking effect ?
The .wrn and .err files receive compiler and linker errors. The warning
you got was issued by the build command itself. And, apparently, build
does not write its warnings to the .wrn file.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.