Driver library

Hi,

I have a driver, which is build from a few libraries (TARGETTYPE=DRIVER_LIBRARY). Is it possible to define for each library a .def file, which defines the exported functions.

I have a few libraries with internal functions with the same name. I am looking for a way to export only the API to avoid mulitple definitions problem.

Thanks,
Shai

DRIVER_LIBRARY defines a library of object modules that gets linked to the
final product, not a DLL, use EXPORT_DRIVER for a kernel mode DLL and then
you can use a .def file.

For the internal functions reorganize the code so you can declare those
functions static then there is no problem.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

wrote in message news:xxxxx@ntdev…
> Hi,
>
> I have a driver, which is build from a few libraries
> (TARGETTYPE=DRIVER_LIBRARY). Is it possible to define for each library a
> .def file, which defines the exported functions.
>
> I have a few libraries with internal functions with the same name. I am
> looking for a way to export only the API to avoid mulitple definitions
> problem.
>
> Thanks,
> Shai
>

This is a .LIB and not a .DLL (DYNLINK) or a .SYS kernel mode DLL
(EXPORT_DRIVER)

So, all non-“static” functions are exported.


Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

wrote in message news:xxxxx@ntdev…
> Hi,
>
> I have a driver, which is build from a few libraries
(TARGETTYPE=DRIVER_LIBRARY). Is it possible to define for each library a .def
file, which defines the exported functions.
>
> I have a few libraries with internal functions with the same name. I am
looking for a way to export only the API to avoid mulitple definitions problem.
>
> Thanks,
> Shai
>