RE: [ntdev] Re: Batch file for Visual Studio build, was Why not use BUILD
[was Re: Errors while building samples of DriverStudio in Windows XP]>
“Bi Chen” wrote in message news:xxxxx@ntdev…
>
>Peter.
>
>I beg to differ. I have been using Visual Studio .dsp for years on more
than dozen of >drivers, long before driverworks was out.
>
>Here is a sample of batch file that is improved from Walter’s batch file
that you can >modify to build your driver for any NT Family OS. It uses
DDK’s own setenv.bat to >set environmental variables and compiler/link to be
used first. Then it allows you to >add additional environmental variables to
fit your project. I keep sources file around >for automatic release build by
QA people
>
Bi… we have nothing (very much) to differ over.
My only contention is: You’ve gotta use the correct tools to build your
driver. Whether you front-end those tools with BUILD, or NMAKE, or
ClearCase, or VS doesn’t matter. You must (a) use the right compiler, (b)
use the right linker, (c) use the right settings.
The only thing that I don’t particularly like about your command procedure
is that it requires you to verify your compile/link flags every time the DDK
is updated. But as long as you do that, and build with the proper compiler
and linker, all is well.
Peter
OSR