Actually, and I know you will find this shocking, I disagree. There is such
a thing as “correct” when it comes to building drivers for windows
platforms, and it is defined as whatever settings build.exe emits for
compiling/linking a driver. “As long as it loads” is a good start, but a bit
too lax.
Finally, using the IDE is not the issue. As you know, as it has been
discussed here ad nauseum, you can use the IDE and also have absolute DDK
compatibility (correctness) by using the ‘external makefile project’
approach as in my infamous ddkbuild batch script.
It is in fact wizards with their built in fixed idea of what the correct
settings were at some point in time for some version of the ddk that is the
problem. Of course if instead you are advocating manually setting the
compilation flags for each project, then in some loose sense ‘wizards’ are
indeed not the issue.
=====================
Mark Roddy
-----Original Message-----
From: Moreira, Alberto [mailto:xxxxx@compuware.com]
Sent: Monday, July 19, 2004 10:18 AM
To: Windows System Software Devs Interest List
Subject: RE: Re[2]: [ntdev] Producing debug information for XP DDK
This has nothing to do with the Wizard. It has to do with using the IDE.
Yes, one needs to know the settings. No, it’s not nearly that difficult, it
takes a few minutes to run build.exe and dump the settings from the log
file. Plus, these things are a lot more static than you’re making it.
Moreover, there’s no such a thing as “correct” here, this is just a .sys
file, and as long as it loads, we’re in business: no need for dirty
compatibility.
And you can trust that DriverStudio will handle it correctly. 
Alberto.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Roddy
Sent: Friday, July 16, 2004 11:03 PM
To: Windows System Software Devs Interest List
Subject: RE: Re[2]: [ntdev] Producing debug information for XP DDK
That is necessary but not sufficient. You also have to go and reverse
engineer all the compiler/linker flags for all possible build types and then
map those onto various flavors of IDE builds. And then every time a new ddk
comes out you have to go do it all over again. Plus if you build against
multiple versions of the ddk, you have to maintain version specific
settings. Seems like a lot of work just to have a wizard I find adding
a new ddk build type to either the ‘dos box’ approach or the ddkbuild
approach trivial, a matter of a few minutes work, and guaranteed correct.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Moreira,
Alberto
Sent: Friday, July 16, 2004 1:50 PM
To: Windows System Software Devs Interest List
Subject: RE: Re[2]: [ntdev] Producing debug information for XP DDK
Just set your tools/options/directories/executable to where your
compiler is.
Alberto.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Robert Newton
Sent: Friday, July 16, 2004 1:40 PM
To: Windows System Software Devs Interest List
Subject: Re[2]: [ntdev] Producing debug information for XP DDK
> The challenge here is that you still are not using the
right compiler,
> and that Microsoft does change the compile switches every
so often.
> Using anything but the DDK environment is one of the
greatest acts of
> stupidity one can do! In fact I know of a firm that
dictated the DDK
> environment,
and
> found out the driver they got was built otherwise, they are
> contemplating suing the supplier for not meeting the reuqirements
> since there were
several
> bugs found by moving to correct environment.
I would agree with this analysis. Using the right compiler is likely
to become more important with time especially as MS attempts to start
supporting C++. It’s just not very hard to produce a Visual Studio
project that will compile using build on the DDK compiler. It will
even still show you compile errors and let go to code by clicking on
the error message (ie., It is pretty much as convenient to use as
compiling with VS6).
Robert Newton
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as:
xxxxx@compuware.com To unsubscribe send a blank email to
xxxxx@lists.osr.com
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.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@compuware.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
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.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@stratus.com To
unsubscribe send a blank email to xxxxx@lists.osr.com