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

List:       kde-core-devel
Subject:    Re: [PATCH] kcmoduleinfo [WAS] Plugin linking problem
From:       David Faure <faure () kde ! org>
Date:       2007-08-09 21:28:32
Message-ID: 200708092328.33212.faure () kde ! org
[Download RAW message or body]

On Tuesday 07 August 2007, Rafael Fernández López wrote:
> Now the problem is solved in a very clean way. The same library, say
> "ktexteditor_docwordcompletion" will ship the plugin and the config
> module itself for letting KPluginSelector load it.

So this is about having one plugin with two entry-points, one for the kcm and one for whatever
else the plugin is about? This should work, as long as the entry points are named differently...
but are they? If both use K_EXPORT_COMPONENT_FACTORY then the entry point is called
init_<libname> for both (see klibloader.h), so if it's a single libname there's a clash. What do I miss?

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

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