> ----------
From: xxxxx@nryan.com[SMTP:xxxxx@nryan.com]
Reply To: xxxxx@lists.osr.com
Sent: Friday, May 23, 2003 11:33 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: XP DDK Compiling
- Nobody says you can’t use external editors to edit C files included
in a VisualC project. I know people who do it all the time.
Sure, I also did it when worked on projects other created this way by
others. The problem is you need VC installed and have to call it for build
which is slower than simple makefile or SOURCES. And create projects there,
start it for every project change. No, thanks.
- Automated nightly builds are incredibly simple with VS NET .2003’s
new solution configurations. I build half-a-million lines of source code
(some as user-mode, some as kernel-mode, some as both) with these three
commands:devenv.com /rebuild “Release” client.sln
devenv.com /rebuild “Release 2kDrv” client.sln
devenv.com /rebuild “Release Nt4Drv” client.slnYou can even force VisualC to use your batch file’s environment instead
of its own directory search paths (in the GUI options) with the /useenv
switch.
It was possible also with older versions; we did it during conversion phase
for old projects. My point was different: how to enforce common
configuration for all projects at one place. Editing every project isn’t an
option, at least not professional option.
- It is true you CAN build user-mode code with the DDK, but that’s not
what it was designed for, was it?
We can only guess. There is support for it inside DDK, even MFC apps can be
build this way. Build utility uses nmake which was surely designed for user
mode code, the rest is just makefile.def i.e common configuration.
As Max pointed out, NT is (or at least was) build this way.
All of the samples in the Platform SDK
use the build tools installed with VisualC.
Just because it is for users who use VS. DDK also contains SDK headers
including STL, I use it for all user mode development.
Yes, I agree that building
kernel-mode code with VisualC was not what that was designed for either,
but my point remains that we need ONE development environment for what
is to me an arbitrary distinction between ‘user-mode’ and ‘kernel-mode’
code.
DDK is quite suitable development environment for both. All you need is
headers, libs, compiler, make and build utilities. Everything else is user’s
choice.
Best regards,
Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]