From: "Davide Pesavento" <pesa@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/qt:master commit in: x11-libs/qt-gui/
Date: Sun, 12 Aug 2012 09:27:33 +0000 (UTC) [thread overview]
Message-ID: <1344763546.e6aae956daebf4a3ea7438469e68de5a2981b2e2.pesa@gentoo> (raw)
commit: e6aae956daebf4a3ea7438469e68de5a2981b2e2
Author: Davide Pesavento <davidepesa <AT> gmail <DOT> com>
AuthorDate: Sun Aug 12 09:25:46 2012 +0000
Commit: Davide Pesavento <pesa <AT> gentoo <DOT> org>
CommitDate: Sun Aug 12 09:25:46 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/qt.git;a=commit;h=e6aae956
[x11-libs/qt-gui:5] Implement several new USE flags, make fontconfig mandatory.
This should also fix bug 430290.
---
x11-libs/qt-gui/metadata.xml | 7 +++-
x11-libs/qt-gui/qt-gui-5.9999.ebuild | 52 ++++++++++++++++++++++++++++------
2 files changed, 48 insertions(+), 11 deletions(-)
diff --git a/x11-libs/qt-gui/metadata.xml b/x11-libs/qt-gui/metadata.xml
index 98454c7..d86d15d 100644
--- a/x11-libs/qt-gui/metadata.xml
+++ b/x11-libs/qt-gui/metadata.xml
@@ -5,13 +5,16 @@
<use>
<flag name="c++0x">Build Qt using the C++11 standard</flag>
<flag name="c++11">Build Qt using the C++11 standard</flag>
- <flag name="egl">Use EGL instead of default GLX to manage OpenGL
- contexts on the desktop</flag>
+ <flag name="egl">Use EGL instead of default GLX to manage OpenGL contexts</flag>
+ <flag name="eglfs">Compile EGL Full Screen/Single Surface support</flag>
+ <flag name="evdev">Enable evdev input support</flag>
<flag name="exceptions">Add support for exceptions - like catching them
inside the event loop (recommended by Nokia)</flag>
+ <flag name="gles2">Use OpenGL ES 2.0 instead of desktop OpenGL</flag>
<flag name="glib">Enable <pkg>dev-libs/glib</pkg> eventloop support</flag>
<flag name="gtkstyle">Build a Qt style called GTK+ that mimics the active
GTK+ theme</flag>
+ <flag name="kms">Enable KMS-based QPA plugin</flag>
<flag name="qt3support">Enable the Qt3Support libraries for Qt4. Note that
this does not mean you can compile pure Qt3 programs with Qt4.</flag>
<flag name="trace">
diff --git a/x11-libs/qt-gui/qt-gui-5.9999.ebuild b/x11-libs/qt-gui/qt-gui-5.9999.ebuild
index 442804d..3ad5546 100644
--- a/x11-libs/qt-gui/qt-gui-5.9999.ebuild
+++ b/x11-libs/qt-gui/qt-gui-5.9999.ebuild
@@ -14,19 +14,34 @@ else
KEYWORDS="~amd64"
fi
-# TODO: directfb, eglfs, kms, linuxfb, evdev, ibus
+# TODO: directfb, linuxfb, ibus
-IUSE="egl +fontconfig gif +glib jpeg opengl +png udev +xcb"
+IUSE="egl eglfs evdev gif gles2 +glib jpeg kms opengl +png udev +xcb"
+REQUIRED_USE="
+ egl? ( gles2 )
+ eglfs? ( egl evdev )
+ gles2? ( opengl )
+ kms? ( egl )
+"
RDEPEND="
+ media-libs/fontconfig
media-libs/freetype:2
sys-libs/zlib
~x11-libs/qt-core-${PV}[debug=,glib=]
egl? ( media-libs/mesa[egl] )
- fontconfig? ( media-libs/fontconfig )
gif? ( media-libs/giflib )
+ gles2? ( || (
+ media-libs/mesa[gles2]
+ media-libs/mesa[gles]
+ ) )
glib? ( dev-libs/glib:2 )
jpeg? ( virtual/jpeg )
+ kms? (
+ media-libs/mesa[gbm]
+ sys-fs/udev
+ x11-libs/libdrm
+ )
opengl? ( virtual/opengl )
png? ( media-libs/libpng:0 )
udev? ( sys-fs/udev )
@@ -41,6 +56,7 @@ RDEPEND="
)
"
DEPEND="${RDEPEND}
+ evdev? ( sys-kernel/linux-headers )
test? ( ~x11-libs/qt-network-${PV}[debug=] )
"
@@ -52,26 +68,44 @@ QT5_TARGET_SUBDIRS=(
)
pkg_setup() {
- QCONFIG_ADD="accessibility
- $(usev fontconfig)
- $(usev opengl)
- $(use udev && echo libudev)"
+ QCONFIG_ADD="
+ accessibility
+ $(usev egl)
+ $(usev eglfs)
+ $(usev evdev)
+ fontconfig
+ $(use gles2 && echo opengles2)
+ $(usev kms)
+ $(usev opengl)
+ $(use udev && echo libudev)
+ $(usev xcb)"
QCONFIG_DEFINE="$(use egl && echo QT_EGL)
+ $(use eglfs && echo QT_EGLFS)
$(use jpeg && echo QT_IMAGEFORMAT_JPEG)"
qt5-build_pkg_setup
}
src_configure() {
+ local opengl="-no-opengl"
+ if use gles2; then
+ opengl="-opengl es2"
+ elif use opengl; then
+ opengl="-opengl desktop"
+ fi
+
local myconf=(
-accessibility
$(qt_use egl)
- $(qt_use fontconfig)
+ $(qt_use eglfs)
+ $(qt_use evdev)
+ -fontconfig
$(use gif || echo -no-gif)
$(qt_use glib)
$(qt_use jpeg libjpeg system)
- $(qt_use opengl)
+ $(qt_use kms)
+ ${opengl}
$(qt_use png libpng system)
$(use udev || echo -no-libudev)
$(use xcb && echo -xcb -xrender)
next reply other threads:[~2012-08-12 9:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 9:27 Davide Pesavento [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-22 8:40 [gentoo-commits] proj/qt:master commit in: x11-libs/qt-gui/ Davide Pesavento
2013-02-13 8:38 Davide Pesavento
2013-01-29 18:04 Michael Palimaka
2013-01-26 11:24 Davide Pesavento
2013-01-25 9:07 Davide Pesavento
2013-01-02 1:15 Davide Pesavento
2012-12-23 3:35 Davide Pesavento
2012-12-10 8:35 Davide Pesavento
2012-11-14 10:28 Davide Pesavento
2012-09-19 23:23 Davide Pesavento
2012-09-03 8:11 Davide Pesavento
2012-08-28 3:06 Davide Pesavento
2012-07-23 18:10 Davide Pesavento
2012-07-22 2:20 Davide Pesavento
2012-07-13 11:19 Ben de Groot
2012-07-05 15:58 Davide Pesavento
2012-07-02 17:26 Davide Pesavento
2012-07-02 16:00 Davide Pesavento
2012-06-10 21:29 Davide Pesavento
2012-05-06 15:09 Davide Pesavento
2012-03-17 15:57 Michael Palimaka
2012-03-11 12:59 Markos Chandras
2012-03-03 9:33 Markos Chandras
2012-02-12 9:17 Markos Chandras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1344763546.e6aae956daebf4a3ea7438469e68de5a2981b2e2.pesa@gentoo \
--to=pesa@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox