From: "Eli Schwartz" <eschwartz@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/gtk-vnc/
Date: Tue, 6 Aug 2024 00:20:06 +0000 (UTC) [thread overview]
Message-ID: <1722903504.14f4be4038afc5a9ffd1a6693469b930cba8f67c.eschwartz@gentoo> (raw)
commit: 14f4be4038afc5a9ffd1a6693469b930cba8f67c
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Sun May 5 20:44:33 2024 +0000
Commit: Eli Schwartz <eschwartz <AT> gentoo <DOT> org>
CommitDate: Tue Aug 6 00:18:24 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=14f4be40
net-libs/gtk-vnc: prevent automagically building against gtk[X,wayland]
e.g. the upstream code checks whether GDK_WINDOWING_WAYLAND is defined
by the gtk headers, and if so will compile against the wayland symbols
it provides. This means that gtk-vnc built on a system with
gtk+[-wayland] will be compatible with anything, but when built on a
system with gtk+[wayland], requires that at runtime.
This cannot be expressed with USE flags.
We could bind tightly to whether gtk was built with wayland (and X), and
in the process, arbitrarily restrict gtk-vnc[-wayland] to only build and
install on a system with gtk+[-wayland].
But we recently added a hack to gtk itself which allows hiding the
automagic macros entirely. Inject this via append-cflags if the USE
flags aren't set, to simulate building on a system with more minimal gtk
packages.
Bug: https://bugs.gentoo.org/624960
Closes: https://bugs.gentoo.org/865659
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Eli Schwartz <eschwartz <AT> gentoo.org>
net-libs/gtk-vnc/gtk-vnc-1.3.1-r1.ebuild | 63 ++++++++++++++++++++++++++++++++
1 file changed, 63 insertions(+)
diff --git a/net-libs/gtk-vnc/gtk-vnc-1.3.1-r1.ebuild b/net-libs/gtk-vnc/gtk-vnc-1.3.1-r1.ebuild
new file mode 100644
index 000000000000..f5ac953e4e80
--- /dev/null
+++ b/net-libs/gtk-vnc/gtk-vnc-1.3.1-r1.ebuild
@@ -0,0 +1,63 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+PYTHON_COMPAT=( python3_{10..12} )
+
+inherit flag-o-matic gnome.org vala meson python-any-r1 xdg
+
+DESCRIPTION="VNC viewer widget for GTK"
+HOMEPAGE="https://wiki.gnome.org/Projects/gtk-vnc https://gitlab.gnome.org/GNOME/gtk-vnc"
+
+LICENSE="LGPL-2.1+"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~ia64 ~loong ~ppc ~ppc64 ~riscv ~sparc ~x86"
+IUSE="+introspection pulseaudio sasl +vala wayland X"
+REQUIRED_USE="vala? ( introspection )"
+
+RDEPEND="
+ >=dev-libs/glib-2.56.0:2
+ >=x11-libs/gdk-pixbuf-2.36.0:2
+ >=dev-libs/libgcrypt-1.8.0:0=
+ >=net-libs/gnutls-3.6.0:0=
+ >=sys-libs/zlib-1.2.11
+ sasl? ( >=dev-libs/cyrus-sasl-2.1.27:2 )
+ >=x11-libs/gtk+-3.24.41-r1:3[introspection?,wayland?,X?]
+ >=x11-libs/cairo-1.15.0
+ >=x11-libs/libX11-1.6.5
+ pulseaudio? ( media-libs/libpulse )
+ introspection? ( >=dev-libs/gobject-introspection-1.56.0:= )
+"
+# Keymap databases code is generated with python3; configure picks up $PYTHON exported from python-any-r1_pkg_setup
+# perl for pod2man
+DEPEND="${RDEPEND}"
+BDEPEND="
+ ${PYTHON_DEPS}
+ >=dev-lang/perl-5
+ dev-util/glib-utils
+ >=sys-devel/gettext-0.19.8
+ virtual/pkgconfig
+ vala? ( $(vala_depend) )
+"
+
+src_prepare() {
+ default
+
+ use vala & vala_setup
+}
+
+src_configure() {
+ # defang automagic dependencies, bug #927952
+ use wayland || append-cflags -DGENTOO_GTK_HIDE_WAYLAND
+ use X || append-cflags -DGENTOO_GTK_HIDE_X11
+
+ local emesonargs=(
+ $(meson_feature introspection)
+ $(meson_feature pulseaudio)
+ $(meson_feature sasl)
+ -Dwith-coroutine=auto # gthread on windows, libc ucontext elsewhere; neither has extra deps
+ $(meson_feature vala with-vala)
+ )
+ meson_src_configure
+}
next reply other threads:[~2024-08-06 0:20 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 0:20 Eli Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-14 2:20 [gentoo-commits] repo/gentoo:master commit in: net-libs/gtk-vnc/ Pacho Ramos
2025-04-14 2:20 Pacho Ramos
2025-04-14 2:20 Pacho Ramos
2024-12-04 18:10 Joonas Niilola
2024-12-04 18:10 Joonas Niilola
2024-08-26 22:57 Sam James
2024-08-09 17:19 Sam James
2024-08-09 17:19 Sam James
2024-06-10 13:55 Stefan Strogin
2024-06-03 7:00 Sam James
2024-01-04 18:11 Arthur Zamarin
2023-09-24 9:02 WANG Xuerui
2022-10-31 14:28 Matt Turner
2022-10-14 14:29 Matt Turner
2022-09-19 1:38 Sam James
2022-09-12 16:01 Sam James
2022-09-12 16:00 Sam James
2022-07-21 2:04 Matt Turner
2022-07-16 21:28 Matt Turner
2022-07-10 23:52 Sam James
2022-07-10 23:15 Sam James
2022-07-10 22:28 Sam James
2022-07-10 19:59 Sam James
2022-01-24 3:39 Sam James
2022-01-20 10:02 Jakov Smolić
2021-12-31 3:42 Yixun Lan
2021-12-17 1:22 Matt Turner
2021-05-08 20:27 Matt Turner
2021-05-07 13:29 Sam James
2021-05-07 13:28 Sam James
2021-04-28 4:21 Matt Turner
2021-04-28 4:21 Matt Turner
2020-07-04 15:07 Mart Raudsepp
2020-06-29 15:42 Mikle Kolyada
2020-06-28 14:19 Thomas Deutschmann
2020-04-05 13:23 Mart Raudsepp
2020-04-04 21:15 Mart Raudsepp
2020-04-04 20:48 Mart Raudsepp
2019-08-04 19:26 Aaron Bauman
2019-05-18 23:05 Mart Raudsepp
2019-03-22 13:29 Mart Raudsepp
2019-03-07 21:14 Mart Raudsepp
2018-12-09 16:04 Gilles Dartiguelongue
2018-12-02 17:27 Mart Raudsepp
2018-12-02 14:29 Mikle Kolyada
2018-12-02 10:12 Mikle Kolyada
2018-11-02 12:54 Mart Raudsepp
2018-08-02 13:50 Mart Raudsepp
2018-04-29 0:08 Mart Raudsepp
2018-04-26 22:32 Aaron Bauman
2018-04-26 17:15 Thomas Deutschmann
2018-04-20 10:36 Mart Raudsepp
2018-04-20 10:36 Mart Raudsepp
2018-04-20 10:36 Mart Raudsepp
2018-04-14 22:41 Mart Raudsepp
2017-10-28 8:43 Pacho Ramos
2017-10-20 14:51 Manuel Rüger
2017-10-03 0:42 Thomas Deutschmann
2017-09-12 6:51 Gilles Dartiguelongue
2017-05-24 8:38 Pacho Ramos
2017-05-24 8:38 Pacho Ramos
2016-10-19 22:02 Gilles Dartiguelongue
2016-09-11 19:00 Gilles Dartiguelongue
2016-09-11 19:00 Gilles Dartiguelongue
2015-09-14 17:18 Pacho Ramos
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=1722903504.14f4be4038afc5a9ffd1a6693469b930cba8f67c.eschwartz@gentoo \
--to=eschwartz@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