Are those C++ symbols all external? [LWN.net]

Are those C++ symbols all external?

Posted Jul 19, 2009 7:36 UTC (Sun) by dirtyepic (guest, #30178)
In reply to: Are those C++ symbols all external? by nix
Parent article: Is pre-linking worth it?

it supposedly does work with KDE 3, or at least I remember us having to disable it repeatedly as support for hidden visibility matured over GCC releases. these days though it works pretty smoothly. note, however, that it's disabled by default. you have to pass --enable-gcc-hidden-visibility to configure at build time.

to post comments

Are those C++ symbols all external?

Posted Jul 19, 2009 11:25 UTC (Sun) by nix (subscriber, #2304) [Link] (2 responses)

Last time I did that it refused, telling me Qt (3.3.8 with security fixes)
didn't have sufficient support. I think it needs distro patches to Qt...

Are those C++ symbols all external?

Posted Jul 20, 2009 4:39 UTC (Mon) by dirtyepic (guest, #30178) [Link] (1 responses)

I think you're right. I never noticed that before. I find it odd that a feature in KDE would require external patches to Qt, but I guess that's the kind of situation they were in at the time.

Are those C++ symbols all external?

Posted Jul 20, 2009 6:50 UTC (Mon) by nix (subscriber, #2304) [Link]

Getting hidden visibility to work with C++ was tricky, as I recall. You
certainly have to appropriately mark ancestors of classes that are being
so marked to get any real reduction in symbol count, which means Qt does
need marking.