Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 405889 - kde-base/kwin-4.8.0: non-opengl-build does not work
Summary: kde-base/kwin-4.8.0: non-opengl-build does not work
Status: RESOLVED DUPLICATE of bug 402029
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-26 12:14 UTC by Hanno Böck
Modified: 2012-02-27 17:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hanno Böck gentoo-dev 2012-02-26 12:14:35 UTC
seems kwin without USE="opengl" build does not work:

-----------------------------------------------------------------------------
-- The following REQUIRED packages could NOT be located on your system.
-- You must install these packages before continuing.
-----------------------------------------------------------------------------
   * OpenGL (ES)  <http://mesa3d.org/>
     OpenGL (ES)
     Either OpenGL or OpenGL ES 2.0 are required for Compositing support in KWin.


Rebuilding kdelibs with USE="opengl" and building kwin with USE="opengl" fixed the problem.

I don't know if kwin works without opengl at all these days, but if this is the case, it should probably dep on kdelibs[opengl].
Comment 1 Andreas K. Hüttel archtester gentoo-dev 2012-02-26 23:26:27 UTC
Yeah well... Some time ago I discussed this with kwin people and they said building without any opengl is not supported anymore.

So whatever condition we place should prevent this case. 

Only thing I'm not sure about- with kwin[gles,-opengl], do we need kdelibs[opengl]?
Comment 2 Michael Palimaka (kensington) gentoo-dev 2012-02-27 08:05:52 UTC
This affects all packages from kde-workspace, see bug #402029.
Comment 3 Johannes Huber (RETIRED) gentoo-dev 2012-02-27 17:47:56 UTC

*** This bug has been marked as a duplicate of bug 402029 ***