trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

Re: Re: [trinity-devel] Re: Resolving the TWin/KWin Fork Issue

From: Martin Gräßlin <mgraesslin@...>
Date: Sun, 29 Apr 2012 00:14:02 +0200
On Saturday 28 April 2012 23:56:01 Julius Schwartzenberg wrote:
> Martin Gräßlin wrote:
> > But honestly I doubt that Ubuntu would include any Trinity specific
> > version of KWin given that there are no other packages for Trinity
> > available.
> Yes, that's true. But wouldn't you agree that this package would be
> suitable for more than just Trinity? :) There are more window-managers
> packaged that are not related to a specific DE. I would treat this
> version of kwin4 as such as well.
That's true, but those window managers can be used standalone (e.g. openbox) 
while that is not the case with KWin. Given the mission statement KWin is not 
meant to be used as a standalone window manager but together with a Desktop 
Shell.

The idea is that each Desktop Shell which uses KWin has to provide it's own 
KWin as currently done by the KDE Plasma Desktop/Netbook workspaces and KDE 
Plasma Active.
> cmake -DNepomuk_FOUND=FALSE -DWITH_OpenGL=OFF -DKWIN_PLASMA_ACTIVE=OFF \
> -DKWIN_BUILD_XRENDER_COMPOSITING=OFF -DKWIN_BUILD_ACTIVITIES=OFF \
> ../kde-workspace
You don't need to have -DKWIN_PLASMA_ACTIVE=OFF - that's the default.

My recommendation would be to keep OpenGL enabled (disabling OpenGL means you 
use OpenGL ES which is not supported by all hardware) and also XRender 
enabled. Turning off Nepomuk btw has no influence on KWin, it's a leftover 
from my Jenkins when I built complete workspace instead of just KWin.

> Are my KDE libraries too old?
no you found a combination which does not build (disabling XRender). I have 
not yet set up my Jenkins to build all combinations. This will be done when we 
are in feature freeze and I have time for such things :-)
> 
> One small thing. Right now it is necessary to check out the complete
> kde-workspace to compile kwin. It would seem easier if kwin would be
> separate from the rest of kde-workspace. Or does kwin depend on most of
> kde-workspace anyhow?
It only depends indirectly. The default window decoration Oxygen requires 
another lib from kde-workspace (can be disabled by build option to turn off 
decorations) and two D-Bus interfaces are generated at compilation.

Unfortunately it is non-trivial to split out kwin from kde-workspace as it's 
one git repository and the code moved around in the past quite often.

Cheers
Martin

Attachments: