KDE_EXPORT question

[Thiago Macieira]

Andras Mantia wrote:
>Hi,
>
> I have a question regarding the above define. Why should every library
>define its own *_EXPORT and not use KDE_EXPORT directly? Is this
>mandatory?

Because of Windows. On Windows, the LIBRARY_EXPORT macro is defined either 
to KDE_EXPORT or to KDE_IMPORT, depending on whether you're building that 
library or just using it.

And since you can only build one library at a time, there's at most one 
_EXPORT that is defined as KDE_EXPORT. All the rest must be KDE_IMPORT.

-- 
Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
  thiago.macieira (AT) trolltech.com     Trolltech AS
    GPG: 0x6EF45358                   |  Sandakerveien 116,
    E067 918B B660 DBD1 105C          |  NO-0402
    966C 33F5 F005 6EF4 5358          |  Oslo, Norway
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060429/129c52f9/attachment.sig>