Ok,
I got it working with DDKBuild.CMD.
Apperently the problem seems to be with the path to the DDKBUILD.CMD when
the project is setup from within visual studio 2008.
I installed DDKBUILD in:
C:\Tools\DDKBUILD
The DDKWizard assumes it's in C:\WINDDK so the wizard can't find it.
Further more my WDK is in:
C:\Tools\WinDDK\6001.18001
This also has to be overriden in the wizard options.
To do this simply check the disabled-looking checkboxes... they are not
really disabled... they just look like that...
That's a gui design mistake by the creator of the wizard.
I setup the path to point directly to the cmd tool and then it works... just
specifieing the folder for the bat approach didn't see to work... the path
and filename must be specified like so:
C:\Tools\DDKBUILD\DDKBUILD.CMD
Now the building for the example drivers works in visual studio 2008... nice
!
It creates to project though... apperently one for windows xp and one for
longhorn or so...
That's kinda weird.
So tool seems a bit old but ok.
Euhm... also I read some of the WDK documentation and it appears the build
tools and possibly the cl.exe compiler has problems with "spaces" in
filenames and paths.
So filenames and paths should not contain spaces...
I find this very annoying and limiting... because all of my development
folders usually contain plenty of spaces...
But to be on the safe side and prevent problems later on it's better to
avoid spaces in filenames and paths all together.
Big question is when will all these compilers finally support spaces in
paths and filenames ?!?
This is not 1992 with dos you know ?! ;)
Bye,
Skybuck.