Re: [kde-artists] oxygen style and kwin client, svn external

Andreas Pakulat <[email protected]>
Newsgroups gmane.comp.kde.artists
Message-ID <20100103123241.GA6425@barmbek>
Resending to kde-artists as suggested by Aaron.

On 30.12.09 12:36:42, Aaron J. Seigo wrote:

only to kwin as this is more a technical problem...

> * create a shared lib in runtime that both the kwin client and qstyle can link 
> against. pros: minimal code dupe; cons: ABI would probably need to committed 
> to so that running random combinations of kdebase-runtime and kdebase-
> workspace would work together, means a bit more time spent in runtime linking 
> (though probably not significant)

IMHO thats not necessary, as long as the SOVERSION of the library is
increased as needed(i.e. with each release that breaks binary
compatibility). Then different versions of the shared library can co-exist
without any problem and the workspace-plugin would use X and the
style-plugin would use version Y.

However this also means that headers might need to be installed as
workspace and runtime are supposed to be buildable standalone.

> * create a static lib in runtime that both kwin client and qstyle can link 
> against. pros: the actual source code is shared, no runtime linkage overhead. 
> cons: the code is duplicated in both plugins. 

IIRC linking a static library into a shared object is problematic. It might
require special linking flags (which I think some distro's really really
dislike) and I think there are even platforms that do not support this at
all. (Not sure if KDE or oxygen is built on those platforms at all)

Andreas

-- 
You are wise, witty, and wonderful, but you spend too much time reading
this sort of trash.
_______________________________________________
kwin mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kwin

______________________________________________________________________________
[email protected] |  https://mail.kde.org/mailman/listinfo/kde-artists
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.