[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-optimize
Subject:    Re: [PATCH] libkdeinit symbol pruning
From:       Karl Vogel <karl.vogel () seagha ! com>
Date:       2004-07-19 12:56:56
Message-ID: 20040719125656.2234.qmail () ktown ! kde ! org
[Download RAW message or body]

On 19 Jul 2004, you wrote in gmane.comp.kde.devel.optimize:

> 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. 

NOTE: yesterday evening I did have a few things that acted strange.. don't 
know if it was caused by this patch or some other stuff I did to my KDE..  
and it was already late, so didn't really look for the cause. Will try to 
have a look at it this evening. 


Things that failed:
- Preferences special button on kicker didn't show menu anymore
- Cookie module seemed broken

probably some other stuff too..

Caveat emptor!
_______________________________________________
Kde-optimize mailing list
Kde-optimize@kde.org
https://mail.kde.org/mailman/listinfo/kde-optimize
[prev in list] [next in list] [prev in thread] [next in thread]