It’s command line oriented, it won’t run if I rename or remove my dos box
for security reasons. It requires maintaining a separate sources file and
possibly dir files. It does not adapt itself to dynamic changes to the
project or the solution. It makes it hard to do things piecewise, for
example, compile files in onesies and twosies without building. Its output
is not integrated with the rest of the IDE. It requires me to jump from
window to window, or to add custom steps to my project.
Sorry, that’s the way it used to be when I was a kid back in the sixties, eh
? But this is the twentieth first century now, time to move on.
Alberto.
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Friday, October 18, 2002 8:13 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Errors while building samples of DriverStudio in
Windows XP
Second, Max, exactly what are the ‘gotchas’ with the ‘external
makefile
project using a shell script to invoke build’ (i.e. ddkbuild)
approach to
integrating visual studio with the ddk ‘development process’?
With this - maybe no gotchas, but the amount of problems people on
this list have with all kinds of SRC2DSP tools is large enough to
un-recommend any of them.
Why not use BUILD? We got the knowledge that .BSC can be created from
BUILD. Any more reasons against BUILD?
Max
You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to %%email.unsub%%
The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.