Shared libraries/DLLs
Jarrett Billingsley
kb3ctd2 at yahoo.com
Thu Jan 31 20:51:46 PST 2008
"Unknown W. Brackets" <unknown at simplemachines.org> wrote in message
news:fnu7l0$2p5l$1 at digitalmars.com...
> This appears to work on Linux. I expected it might work (or there might
> be some way to coax it to work) on Windows. It seems logical, even not
> having used the LoadLibrary/etc. stuff before. The library needs to
> access the caller's functions.
>
> It does appear I can make it at least *compile* (but not run) by adding an
> IMPORTS directive to the .def file of the library, but this clearly is
> intended for static linking. I'm wanting to load the DLL as a plugin,
> dynamically. Its name and location might change.
>
> Am I making some hopefully obvious and stupid mistake? Please tell me I
> don't actually have to send pointers to all the api functions to the DLL
> when calling it.
So, uh, what _exactly_ is the problem? I don't think you ever said..
More information about the Digitalmars-d-learn
mailing list