kdeinit (was: Summary from Buildsystem BoF at Desktop Summit)

Alexander Neundorf neundorf at kde.org
Tue Aug 16 19:53:45 BST 2011

On Tuesday 16 August 2011, Thiago Macieira wrote:
> On Tuesday, 16 de August de 2011 19:36:17 Alexander Neundorf wrote:
> > The idea here was not to get rid of this mechanism completely.
> > If I understood correctly, with a PIE executable it is possible to dlopen
> > the  executable and call a symbol from it.
> > This would make it possible to simply create regular-looking, standalone
> > executables instead of the combination of plugin+tiny executable, and at
> > the  same time keep the kdeinit instance around, which would then not
> > dlopen the plugin, but dlopen the PIE executable, and call the symbol
> > from the PIE executable instead of from the plugin, this way providing
> > the same benefits as we have now.
> Ah, that makes a lot more sense. It's also closer to what the Harmattan
> booster does: it dlopens the actual binaries, not a kdenit module.
> However, it's still not perfectly correct: the issue is the difference
> between -fPIE and -fPIC. In a PIE, the compiler and linker *know* that
> this ELF module is the first open loaded,

Sorry, I don't understand that sentence. Is there something missing ?
Linker as in build time linker, or the loader ?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20110816/7f277324/attachment.htm>
-------------- next part --------------
Kde-buildsystem mailing list
Kde-buildsystem at kde.org

More information about the kde-core-devel mailing list