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

List:       kde-core-devel
Subject:    Re: plugins vs. libraries
From:       Stephan Kulow <coolo () kde ! org>
Date:       2002-02-19 21:01:57
[Download RAW message or body]

On Dienstag, 19. Februar 2002 21:44, Waldo Bastian wrote:
> On Tuesday 19 February 2002 06:11 am, Stephan Kulow wrote:
> > Hi!
> >
> > There seem to be a large confusion about plugins vs. libraries.
> > E.g. lib/kde3 contains a lot of modules that start with lib.
> >
> > So let me state my opinion how things should be (and how I will
> > change things to be if noone objects :):
> >
> > libraries
> > ----------
> >   - are installed into $KDEDIRS/lib
> >   - have a version
> >   - a defined interface (i.e. headers)
> >   - are prefixed with lib
> >
> > plugins
> > ---------
> >   - are installed into $KDEDIRS/lib/kde*
> >   - have a very minimal interface (one or two functions having C linkage)
> >   - have no version
> >   - have no lib prefix, but are prefixed with the purpose
> >    (e.g. kcm_, kwin_, kimgio_, etc.)
>
> Sounds fine, what about kded modules? Shouldn't they be named
> "kded_<modulename>.la" as well then?
I don't know about kded modules. But I think so.
>
> What about KDEinit loadable modules? They are currently installed in /lib
> because we link dummy.cpp against them to get executable binaries.
I know. Their interface is even smaller ;(
I still have hopes that kdeinit will disappear someone later this year - I'm 
really unsure how to handle that hack in the best way. So far I'd stay with 
the way it works.

Greetings, Stephan

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