can't see the build error messages

NTDEV
1

Hi,

I am using DDK 3790.1830 to build a small driver. Whenever I execute the BUILD command in the source directory the compiler error only goes the the log file. How can I get them to be displayed on the screen (stdout)?

Thanks,
KH

2

if you can accept a little delay in seeing them ie after build has
completed and log file has been created
cd /d “path to log file”
type foo.log | more

On 6/8/07, xxxxx@khcon.com wrote:
> Hi,
>
> I am using DDK 3790.1830 to build a small driver. Whenever I execute the BUILD command in the source directory the compiler error only goes the the log file. How can I get them to be displayed on the screen (stdout)?
>
> Thanks,
> KH
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>

3

wrote in message news:xxxxx@ntdev…
> Hi,
>
> I am using DDK 3790.1830 to build a small driver. Whenever I execute the
> BUILD command in the source directory the compiler error only goes the the
> log file. How can I get them to be displayed on the screen (stdout)?

Have you used a command line switch to suppress it? -h, perhaps? The
default behavior is errors on screen, warnings only to the log. I use -eFgw
for a build, and -ceFgw for a rebuild, and I’ve always had the output on the
screen.

build /? is your friend here.

Phil
–
Philip D. Barila
Seagate Technology LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.

4

Thanks Phil but this didn’t make a difference.

I was always wondering why the linker would start even though the compile didn’t work, that just didn’t make sense. When I tried building another source I suddenly got an error displayed on the screen and build didn’t call the linker. What was different? The module causing the error message didn’t have a space in the path name and after moving the sources into a folder without blanks in the path I got all the errors I wanted (not that I was crazy to see any errors :wink: ). Apparently the build program can’t handle those spaces and thinks everything is OK…

I needed those errors on the screen because I am using UltraEdit to edit the source and have it execute a batch file in the background to compile. It then captures the output and allows me to jump directly to the offending line in the source.

Thanks guys,
KH

5

After a few years you just automatically stop ever using any pathnames with spaces for development without thinking about it. It has become an unwritten rule.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-289607-
xxxxx@lists.osr.com] On Behalf Of xxxxx@khcon.com
Sent: Saturday, June 09, 2007 8:21 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] can’t see the build error messages

Thanks Phil but this didn’t make a difference.

I was always wondering why the linker would start even though the
compile didn’t work, that just didn’t make sense. When I tried building
another source I suddenly got an error displayed on the screen and
build didn’t call the linker. What was different? The module causing
the error message didn’t have a space in the path name and after moving
the sources into a folder without blanks in the path I got all the
errors I wanted (not that I was crazy to see any errors :wink: ).
Apparently the build program can’t handle those spaces and thinks
everything is OK…

I needed those errors on the screen because I am using UltraEdit to
edit the source and have it execute a batch file in the background to
compile. It then captures the output and allows me to jump directly to
the offending line in the source.

Thanks guys,
KH

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer