Export driver creates LIB which references DLL?!

NTDEV
1

Hello,

today I built an export driver and succeeded in compiling and linking.
However, after having a look at the import table, I found that the importing
driver linked to the export driver via the name .dll instead of
.sys! This is inherited from the LIB file which is produced from
the export driver (find my sources file below)

Can I somehow circumvent this? I could not find any mentioning of this
behavior in the MS documentation (also on the web).

At http://www.microsoft.com/whdc/driver/tips/KmDLL.mspx is is even stated,
that there is no difference between an export driver and a normal driver
during the build process.

-----------------
SOURCES file
-----------------
TARGETNAME=expdrv
TARGETPATH=obj
TARGETTYPE=EXPORT_DRIVER

BUILD_PRODUCES=ExportDrv

SOURCES=expdrv.c <br> drvversion.rc
-----------------

Thanks for any helpful comments,

Oliver

2

It all works fine. Regardless of the dll vs sys issue, your export
driver will be loaded and used to resolve the client’s links to it.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Oliver Schneider
Sent: Tuesday, February 14, 2006 2:48 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Export driver creates LIB which references DLL?!

Hello,

today I built an export driver and succeeded in compiling and linking.
However, after having a look at the import table, I found that the
importing
driver linked to the export driver via the name .dll instead of
.sys! This is inherited from the LIB file which is produced
from
the export driver (find my sources file below)

Can I somehow circumvent this? I could not find any mentioning of this
behavior in the MS documentation (also on the web).

At http://www.microsoft.com/whdc/driver/tips/KmDLL.mspx is is even
stated,
that there is no difference between an export driver and a normal driver
during the build process.

-----------------
SOURCES file
-----------------
TARGETNAME=expdrv
TARGETPATH=obj
TARGETTYPE=EXPORT_DRIVER

BUILD_PRODUCES=ExportDrv

SOURCES=expdrv.c <br> drvversion.rc
-----------------

Thanks for any helpful comments,

Oliver

—
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

3

Mark,

It all works fine. Regardless of the dll vs sys issue, your export
driver will be loaded and used to resolve the client’s links to it.
Sadly it doesn’t. But that’s not a problem anymore. After trying even
passing linker options through the SOURCES file (where /OUT: wouldn’t work),
I figured out that I gave no “NAME” in the .def file - and that was the
problem. This directive is not mandatory and thus I omitted it, because my
driver was not based on some sample driver.

Thanks,

Oliver

–

May the source be with you, stranger :wink:

ICQ: #281645
URL: http://assarbad.net