Re: [PATCH] libkdeinit symbol pruning
David Faure <[email protected]>
| Newsgroups | gmane.comp.kde.devel.optimize |
|---|---|
| Organization | KDE |
| Message-ID | <[email protected]> |
On Monday 19 July 2004 14:16, Waldo Bastian wrote: > On Monday 19 July 2004 13:10, David Faure wrote: > > > What if an application defines a plugin API that plugins can call? > > > > That API would have to be implemented in a _library_. > > You can't implement it in a module, since linking to a module is unportable > > (breaks on BSD I think, on Mac OS X for sure). > > I don't mean linking, I mean plugins that have unresolved symbols that happen > to be provided by the application that loads the plugin. But maybe we got rid > of such plugins already indeed. Ah, and obviously those symbols currently end up being found in the kdeinit module, linked to by the binary, so the symbol pruning would break it. You're right, this might happen. Well, that's a good reason for testing this locally and only applying after 3.3. -- David Faure, [email protected], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).