WITH_PREFIX for kdemodules?

Alexander Neundorf neundorf at kde.org
Mon Nov 5 21:06:19 GMT 2007

On Monday 05 November 2007, David Faure wrote:
> On Monday 05 November 2007, Thiago Macieira wrote:
> > Em Monday 05 November 2007 16:08:48 David Faure escreveu:
> > > We used to do that everywhere (e.g. in all of koffice), but we had to
> > > change it because it broke things on Mac OS X. So I am quite surprised
> > > to read from Thiago that with kde4 and cmake linking to a plugin would
> > > actually be possible; this would certainly simplify things if it's
> > > really true...
> >
> > I didn't say you can link to a plugin everywhere. I said you can dlopen a
> > library everywhere.
> Okay, thanks for the clarification. This leads to the same result though:
> we could make everything libraries and also make them provide a plugin
> entry point where needed (like koffice parts). OK this is a bit dirty in
> general though, especially with the new K_EXPORT_PLUGIN stuff, since we can
> only provide one plugin entry point per "library". So maybe we should keep
> doing it the clean way instead :-)

Ok. So this means if every plugin would have the "lib" prefix we could link to 
every plugin (maybe on all platforms).
If the plugin doesn't have the "lib" prefix, we can't link to it (at least on 
some platforms).

So we have three options:
1) leave it as it is and keep the "WITH_PREFIX" option, so some plugins have 
the "lib" prefix and others don't

2) remove the WITH_PREFIX option and always use the "lib" prefix -> should 
bring no problems, may look at bit ugly, probably also doesn't bring any 

3) remove the WITH_PREFIX option, never use the "lib" prefix -> slightly nicer 
code, linking to a plugin not possible (since -lkfoo won't find kfoo.so)

If it's no problem for us that we cannot link to a plugin I'd vote for 3)


More information about the kde-core-devel mailing list