Hi,
I want to wrap a bunch of helper routines into a kernel dll so that
other drivers can call those helper routines directely.
I use the type EXPORT_DRIVER in SOURCES file
and provide a .DEF file that lists the exportsDLL. The dll can be
build if I use build application.
But if I use MS VC enviroment to build this kernel dll, I can
not get the library file. Only sys file can be generated. I compared
my project setting with the generic.sys example that provided in
Walter Oney’s book. I didn’t find any special different. But If I build
generic.sys, I can get the library file. For my own project file, only
sys file can be generated.
Does anybody know how to build a kernel dll in VC project? Any info
will be appreciated.
I do it all the time. I use DDKBUILD.BAT from www.osr.com in Visual Studio
to do the builds.
–
Mark Cariddi
Consulting Associate
OSR, Open Systems Resources, Inc.
http://www.osr.com/
wrote in message news:xxxxx@ntdev…
>
> Hi,
> I want to wrap a bunch of helper routines into a kernel dll so that
> other drivers can call those helper routines directely.
> I use the type EXPORT_DRIVER in SOURCES file
> and provide a .DEF file that lists the exportsDLL. The dll can be
> build if I use build application.
> But if I use MS VC enviroment to build this kernel dll, I can
> not get the library file. Only sys file can be generated. I compared
> my project setting with the generic.sys example that provided in
> Walter Oney’s book. I didn’t find any special different. But If I build
> generic.sys, I can get the library file. For my own project file, only
> sys file can be generated.
>
> Does anybody know how to build a kernel dll in VC project? Any info
> will be appreciated.
>
>
As we know, using ddkbuild (at least Mark Roddy’s) turns Visual Studio
into a shell for standard build. The question, however, is how to do it
through Visual Studio used “natively.” But, frankly, I wouldn’t bother.
As you say, ddkbuild is adequate and, for the less than expert at Visual
Studio cum build (like me), safer.
–
If replying by e-mail, please remove “nospam.” from the address.
James Antognini