Static plugins and enable final

Thiago Macieira thiago at
Tue Jan 26 12:41:10 GMT 2010

Em Terça-feira 26 Janeiro 2010, às 09:29:13, Dario Freddi escreveu:
> > > I see. I'd prefer to keep the plugin system alive. What would you
> > > advise, using dynamic qt plugins or going straight with KService? My
> > > situation is that, as you can imagine, I have a single plugin to load,
> > > so I think it would be better to go with the first.
> >
> > 
> >
> > If there's only one plugin ever, I recommend you remove the plugin
> > system. Just make it part of the library and bypass all QPluginLoader
> > code.
> The matter is quite simple: having a (dynamic) plugin system would let me 
> avoid linking kdecore to polkit/authorization services/etc, which is
> something  some people would appreciate. Anyway, I'll probably go ahead
> and ditch the plugin system for now. For 4.5 we'll see, now the matter
> needs a fast and definitive solution.

If you want to make plugins, then make plugins (separate .so files).

If you want code in kdecore, then make code in kdecore.

What you made was code in kdecore that was found through the Qt plugin system.

Thiago Macieira - thiago (AT) - thiago (AT)
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the kde-core-devel mailing list