I disagree with Maxim. There are plenty of commercial, closed-source,
products that ship implibs and dlls for C++ class APIs. Responsible vendors
make then available in multiple versions for the various compiler versions.
In the case at hand, I guess someone never considered the DDK as a
possiblity.
Ironically, the obvious way around this (COM) is hardly helpful in the case
at hand.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David Burg
Sent: Tuesday, June 14, 2005 1:57 PM
To: Windows System Software Devs Interest List
Subject: (resent after Lyris bounce) Re: [ntdev] VS C++ 2003 vs WinDDK 2k3
SP1, incompatible compiler mangling?
Dear Maxim,
It’s not a dll, it is a .lib file (for static linking then).
Best regards,
David Burg,
Nero AG.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Monday, June 06, 2005 6:46 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] VS C++ 2003 vs WinDDK 2k3 SP1, incompatible compiler
mangling?
Exporting the C++ mangled names from the DLLs shipped as a toolkit to
3rd parties without sources is a very, very dirty thing.
Can you choose another library (open source, for instance) or develop
the thing in house?
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@dchbk.us
To unsubscribe send a blank email to xxxxx@lists.osr.com