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

List:       kde-optimize
Subject:    Re: [PATCH] libkdeinit symbol pruning
From:       Waldo Bastian <bastian () kde ! org>
Date:       2004-07-19 10:50:07
Message-ID: 200407191304.07671.bastian () kde ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 19 July 2004 02:05, David Faure wrote:
> On Monday 19 July 2004 01:06, Karl Vogel wrote:
> > It will break apps that link to the libkdeinit_*.so's or dlopen them and
> > try to resolve symbols other than kdemain... but I guess if any app does
> > that, then it's already broken by violating the kde abi, no?!
>
> Thinking about it, I'm not sure anyone links to a kdeinit module.
> What people do, which is unportable, is to link to a kparts part, but
> that's unrelated.

What if an application defines a plugin API that plugins can call? (Or worse, 
if the application doesn't define an API and plugins just call stuff all over 
the place) I guess the right thing to do is to give applications the 
opportunity to specify their own export map if they need to export additional 
symbols.

Cheers,
Waldo
- -- 
bastian@kde.org  |   KDE Community World Summit 2004  |  bastian@suse.com
bastian@kde.org  | 21-29 August, Ludwigsburg, Germany |  bastian@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFA+6qnN4pvrENfboIRAkHqAJ95g918nP2u4+5BSw9sI/KUNx3fIACeOi9x
AGpIWjSEkLnxXivZwFIives=
=7SfF
-----END PGP SIGNATURE-----
_______________________________________________
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]