“Moreira, Alberto” wrote in message
news:xxxxx@ntdev…
>
> One more thing: for the diehards, we put a “build” button on the IDE, that
> builds through build.exe in the good old fashioned way. So, what do you
> know, we give you a choice !
>
Gosh! That’s good news. Thank whoever did that for me, will ya?
(note that I never said DriverWorks did not build drivers properly… just
that using the wrong TOOLS (and settings) results in drivers being built
improperly.)
Now EVERYbody’s happy. Almost.
Now, please, just make SRC2DSP a tools that can ONLY be used to import a
project to DriverWorks. And not make it available to devs in the general
developer community who (a) might not own DriverWorks, and (b) might not
understand the consequences of the implicit they’re making by not using the
correct tools to build their drivers.
Please?
Anybody who’s smart enough to elect to use the IDE over BUILD (on their own,
outside of DriverWorks) should be smart enough to be able to convert their
sources file and the appropriate compiler and linker flags to a VS project.
This is still NOT a good idea, in any way, but at least they’re making a
conscious decision. So, when the next rev of the DDK is released, and it
contains a new compiler or a new set of flags, and they lose out or their
driver is incompatible in some weird way… they have nobody to blame but
themselves.
Peter
OSR