Patch for dcop & win32

[David Faure]

On Sunday 16 October 2005 22:42, Thiago Macieira wrote:
> Let me take the opportunity to understand something about DLLs on Windows: 
> does at least one compiler require you to specify each and every 
> dllimport and dllexport?
Yes, apparently. Otherwise Qt wouldn't bother doing that too...

> This will impose a serious problem for KDE libraries because:
> a) we have a great deal of them
So? It's only a matter of defining the proper macros, see kdelibs_export.h
(and koffice_export.h in koffice for the same thing there)

> b) our developers aren't aware of this need and will therefore use the 
> wrong macros
Well, we'll teach them :)
It's quite obvious anyway, once you see KOFFICEUI_EXPORT in all
kofficeui classes, you use it for new kofficeui classes; the scheme
is self-documenting :)

> c) bksys will have to define a macro for each target being built, just 
> like MSVC
The MAKE_FOOLIB macro? Yep; maybe we can automate that part
a little bit in bksys.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).