Static plugins and enable final

John Tapsell johnflux at gmail.com
Tue Jan 26 00:30:30 GMT 2010


2010/1/25 Dario Freddi <drf54321 at gmail.com>:
> On Monday 25 January 2010 23:13:03 Thiago Macieira wrote:
>> Static plugins is discouraged.
>>
>> Long-term solution is to get rid of them.
>>
>> Static plugins is for applications built with static Qt. Since Qt is
>>  static, it can't load a plugin that links to Qt. So the plugins are built
>>  as a static libraries, which are linked to the target program.
>>
>> Static plugins were not meant for dynamic Qt, much less for dynamic
>>  libraries.
>>
>> So please get rid of them, either by removing the plugin system and simply
>> making the code part of the library, or by making it an actual plugin (an
>>  .so file) that is loaded at run-time.
>
> I see. I'd prefer to keep the plugin system alive.

For what reason?  The code without a plugin system would be extremely
close to what you have now.  I don't see why you'd need to hardcode
anything more than you do now?  What are you trying to achieve?

John




More information about the kde-core-devel mailing list