> -----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Thursday, June 11, 2009 7:14 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] SURVEY: Using more than one version of the WDK1… In normal work do you have more than one version of the
WDK in use?
Sure, always.
If so why?
Because we have drivers which were developed, debugged and tested using
older WDKs. Some of them didn’t change for years. Wy to invest all the
time to new testing and qualification? And risk a problem at customers’
machines?
Of course, new driver for Win7 is developed using new WDKs updated
regularly (though not every version). But for XP/Vista driver which some
customers use also at Win7 I still use older one and don’t see any
reason to change. That’s the point: there has to be a good reason to
change and pure existence of new version isn’t.
2… When the WDK beta comes out, do you try it with current
projects? If
so do you try to use the same copy of the sources for both,
or clone one
specifically for the beta?
Only for Win7 project under development.
3… Have you encountered problems with using more than one
WDK? Would you
like to have a way to conditionalize the build files or the
driver source
for differing WDK versions?
Yes. We use WDK build as one relatively small sub-task of whole build.
Our buildengine prepares environment, calls requested setenv.bat and
finally build.exe. Any change in setenv/build parameters of behaviour
causes problems and makes builder more complicated. One example:
amd64/x64. No problem if changes are backward compatible but they
sometimes aren’t. Worse problem is in SOURCES, I tend to use make
snippets for standard tasks (as generating version info for example) and
include them in SOURCES.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]