win32 build stops with linker error

Thiago Macieira thiago at kde.org
Wed Feb 15 16:11:40 CET 2006


Peter Kümmel wrote:
>Thiago Macieira wrote:
>> David Faure wrote:
>>>> But then you should use KDE_EXPORT instead!
>>>
>>> For unix KIO_EXPORT or KDE_EXPORT is the same, so I'll trust you to
>>> use whichever works for the Windows side, I'm just surprised that all
>>> libs reading that .h would think that they need to export the symbol
>>> again...
>>
>> They're weak symbols. The dynamic linker chooses one copy (any of
>> them) of the symbol and that's it.
>>
>> And about templates, they won't be exported on ELF platforms unless
>> used -- and then only those symbols that were used.
>>
>> For instance, libQtCore.so exports a total of 0 QMap symbols.
>
>If it makes no sense for Gcc & Co. I've no problem ifdefing the line,
>but msvc needs it.

If it has no sideeffects on ELF platforms, it's ok.

But does this mean that, every time we derive from a template-based class, 
we have to add this same kind of trickery?

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

5. Swa he géanhwearf tó timbran, and hwonne he cóm, lá! Unix cwæð "Hello, 
World". Ǽfre ǽghwilc wæs glæd and seo woruld wæs fréo.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20060215/fd4d99a2/attachment.pgp 


More information about the Kde-buildsystem mailing list