Sometimes when I run the 'build' utility in DDK, it fails with no errors
printing (at least not visible in the DOS windows output). But if I open the
log file, there may be lots of errors listed in there.

Is there a way to ensure that the build utility is always printing ALL
errors and warnings back to stdout or stderr?


Thanks,

/ Hannes.

Create a batch file to start execution. Use ddkbuild.bat from that batch
file. When control returns from the call to ddkbuild.bat, then look for the
warning and error files being present and type them.

"Hannes" <hannes.news@nospam.nospam> wrote in message
news:86D57D49-C004-459C-89FB-37DADB9DFB66@microsoft.com...

David Craig wrote:
mode' (credit goes to Beverly Brown at Mercury Systems for this
enhancement) that will limit ddkbuild's output to stdout to ONLY errors
and warnings, making it much easier to trigger alarms in automated build
systems.


--

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

"build -w" will do IIRC.

--
Calvin Guan Windows DDK MVP
Staff SW Engineer, NetXtreme MINIPORT
Enterprise Network Controller Engineering
Broadcom Corporation www.broadcom.com


"Hannes" <hannes.news@nospam.nospam> wrote in message
news:86D57D49-C004-459C-89FB-37DADB9DFB66@microsoft.com...

"Calvin Guan" wrote:
Nope, the '-w' option does not seem to make any difference for me.

/ Hannes.

I am looking forward to that! I am already modifying each version of
DDKBUILD.BAT to remove a lot of "noise", mainly by commenting out comments
and outputs from DDKBUILD.BAT, but also by changing this line:

%prefast% build %bflags% %mpFlag% %moreExtraArgs%

to this:

%prefast% build %bflags% %mpFlag% %moreExtraArgs% 2>&1 | find /V "BUILD: "
| find /V "Linking Executable" | find /V " files compiled" | find /V "
executable built" | find /V " source files (" | find /V "Copyright (C)
Microsoft Corporation. All rights reserved." | find /V
"-----------------------------------------------------------------------------"
| find /V "Removing duplicate defects from the log..." | find /V "Enter
PREFAST "


Thanks,

/ Hannes.

Here's a simple way to reproduce (for me) in case anyone wants to try it:

In a good source file that includes <ndis.h>, I simply add
#include "windows.h"
above the ndis.h include. This will lead to lots of duplicate definitions
and such - and none of this is reported back to the VS GUI. But there are
lots of errors and warnings in the *.log and *.err files.

/ Hannes.

This does, of course, ensure that I see ALL errors and warnings.

However, I am currently using DDKBUILD, which already prints most errors and
warnings directly back to the VS Output Window. If I in addition to that dump
the contents of *.err and *.log, then I will end up with double or triple
messages in the window, which is not desirable.

/ Hannes.

"David Craig" wrote: