[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:       "=?UTF-8?Q?Rafael_Fern=C3=A1ndez_L=C3=B3pez?=" <ereslibre () gmail ! com>
Date:       2007-08-09 22:17:48
Message-ID: 93f85fee0708091517n46fd4e55u512c2b2875f34510 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (text/plain)]

>
> Ah -- OK. That's cheating :)
> The first argument to K_EXPORT_COMPONENT_FACTORY is supposed to be the
> libname,
> but in this case it's something else.


That is what it was supposed to be, but no. The documentation there I think
wasn't very clear. Is the FactoryName. What happens is that in case that the
X-KDE-FactoryName is missed in a .desktop file, X-KDE-Library is taken in
its place. So yeah, it is the library in the case that X-KDE-FactoryName is
not provided on the .desktop file.

#  define Q_EXPORT_PLUGIN2(PLUGIN, PLUGINCLASS)      \
>             Q_PLUGIN_VERIFICATION_DATA \
>             Q_EXTERN_C Q_DECL_EXPORT \
>             const char * Q_STANDARD_CALL
> qt_plugin_query_verification_data() \
>             { return qt_plugin_verification_data; } \
>             Q_EXTERN_C Q_DECL_EXPORT QObject * Q_STANDARD_CALL
> qt_plugin_instance() \
>             Q_PLUGIN_INSTANCE(PLUGINCLASS)
> So surely this doesn't allow to export more than one plugin from a
> plugin-library, does it?


Hmm... is a pity. It was really nice a library could provide more than one
service (call it plugin, kcmodule, or whatever). So, I commit my changes for
Monday or I leave them ?

I think we could do something on KDE for allowing a library provide more
than one service, that sounds a bit poor to me :(


Bye and thanks,
Rafael Fernández López.

[Attachment #3 (text/html)]

<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Ah -- OK. That&#39;s cheating \
:)<br>The first argument to K_EXPORT_COMPONENT_FACTORY is supposed to be the libname, \
<br>but in this case it&#39;s something else. </blockquote><div><br>That is what it \
was supposed to be, but no. The documentation there I think wasn&#39;t very clear. Is \
the FactoryName. What happens is that in case that the X-KDE-FactoryName is missed in \
a .desktop file, X-KDE-Library is taken in its place. So yeah, it is the library in \
the case that X-KDE-FactoryName is not provided on the .desktop file.&nbsp; \
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">#&nbsp;&nbsp;define \
Q_EXPORT_PLUGIN2(PLUGIN, \
PLUGINCLASS)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Q_PLUGIN_VERIFICATION_DATA \
\ <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Q_EXTERN_C \
Q_DECL_EXPORT \<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;const \
char * Q_STANDARD_CALL qt_plugin_query_verification_data() \
\<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{ return \
qt_plugin_verification_data; } \
\<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Q_EXTERN_C \
Q_DECL_EXPORT QObject * Q_STANDARD_CALL qt_plugin_instance() \ \
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Q_PLUGIN_INSTANCE(PLUGINCLASS)<br>So \
surely this doesn&#39;t allow to export more than one plugin from a plugin-library, \
does it?</blockquote><div><br>Hmm... is a pity. It was really nice a library could \
provide more than one service (call it plugin, kcmodule, or whatever). So, I commit \
my changes for Monday or I leave them ? <br><br>I think we could do something on KDE \
for allowing a library provide more than one service, that sounds a bit poor to me \
:(<br></div></div><br><br>Bye and thanks,<br>Rafael Fernández López.



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