[QKW PATCH] dcopidl/win32

Ralf Habacker Ralf.Habacker at freenet.de
Mon Apr 28 22:27:53 BST 2003


>
> I answer all your question at one time. To do this I must instroduce some
> (aaargh! ;) knowledge from win32 development word. On linux, where quite
> much of linkage suff coming from solaris, every symbol is (at least by
> default) exported to shared libraries, so then can be reused easly.
>
> On win32 every such symbol (specifically for us: the class name), must be
> explicity tagged, to be exported or not. Not exported symbols are then not
> resolved during runtime. There are two methods of making export information
> available to linker:

> 1. Create export file and update it any time then code seems to be changed.
> It is (often) dependent on linker vendor (!) and inconvenient.
> 2. Add special flags to class declarations that we want to make available in
> library. To do this, we should use __declspec(dllexport) in .h file, e.g.:
>
This is only true, if you don't use g++/ld (mingw or cygwin based) on win32,
because the mingw/cygwin ld contains special support to ensure mostly linux
compatibility on windows. With this feature, the kde-cygwin releases could be
build without any of this dump declspec stuff.

Regards
Ralf Habacker
KDE-cygwin http://cygwin.kde.org






More information about the kde-core-devel mailing list