> ----------
From: xxxxx@yoshimuni.com[SMTP:xxxxx@yoshimuni.com]
Reply To: xxxxx@lists.osr.com
Sent: Friday, October 18, 2002 9:30 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] Re: Why not use BUILD [was Re: Errors while building
samples of DriverStudio in Windows XP]I have a setup I like and it works. I use CodeWright for editing and each
project has a batch file that invokes the correct DDK’s setenv.bat and the
compiler’s setup file. I can build 9x drivers with the 98 DDK, DOS
command
line utilities with VC 1.52c, NT4, W2K, & XP drivers with the appropriate
DDK. It takes a little setup, but I find it useful for me. CodeWright
supports the Microsoft browser file format when I need to use it.
It is very similar to my environment; the only real difference is I use
Multi-Edit for editing. Also, we developed a nighty build engine for
internal use which builds all our code including drivers and VxDs; it uses
same batches for environment settings and utilities for building so there is
no difference between code I debug and the result of nighty build. And when
we ship something, the build number is enough to find exact sources and
create exact binary from perforce archives if a problem occurs.
I do use
the IDE for application code whenever I need to compile that, but it isn’t
very often.
For this purpose I use the same approach as for drivers. Environment setting
batch + SOURCES or makefile or our build engine script, which fits better
for given app. I haven’t use VC IDE for years and I’m quite happy with it
Best regards,
Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]