From: Katy and Steve Lee <lee@fu...> - 2002-10-27 18:58:07
> Yes. The idea is that a shared library is the same as a static
> library, but linked at run time (In practice, this goal is not
> achieved. There are still important differences, mostly wrt
> initialization of C++ objects). So, the autoexport feature exports all
> symbols that would be available from a static library.
Ah I meant the C keyword 'static' which is unfortunately overloaded to mean
both 'not automatic' and 'private to this translation unit', I was referring
to the latter. Nothing to do with static/dynamic library linkage. Anyway a
quick play with depends (go get it at http://www.dependencywalker.com if you
haven't got it - indispensable for any DLL issues), proved this is true and
just what the doctor ordered
I get what I need using __stdcall, not using and explicit exports so all are
exported automatically and using the linker option --add-stdcall-alias. This
simulates the _pascal style exports without the need for a def file. I
thought I would hit a problem with case but that has been ok (I think
LoadLibrary() may ignore case case).
Get latest updates about Open Source Projects, Conferences and News.