From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] libgtk3: gdk-wayland backend depends on libX11
Date: Tue, 14 Mar 2017 17:22:54 +0100 [thread overview]
Message-ID: <20170314172254.367744f2@free-electrons.com> (raw)
In-Reply-To: <20170314114628.10147-2-Vincent.Riera@imgtec.com>
Hello,
On Tue, 14 Mar 2017 11:46:27 +0000, Vicente Olivert Riera wrote:
> config BR2_PACKAGE_LIBGTK3_WAYLAND
> bool "Wayland GDK backend"
> default y
> depends on BR2_PACKAGE_HAS_LIBEGL_WAYLAND
> depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_17
> + depends on BR2_PACKAGE_XLIB_LIBX11
This feels weird. Isn't the point of the Wayland backend specifically
to be used with Wayland, and therefore not to depend on anything X.org
related?
Isn't this a bug in Gtk, rather than something we should fix with an
additional dependency?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-14 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 11:46 [Buildroot] [PATCH 1/3] libgtk3: remove non-existent configure options Vicente Olivert Riera
2017-03-14 11:46 ` [Buildroot] [PATCH 2/3] libgtk3: gdk-wayland backend depends on libX11 Vicente Olivert Riera
2017-03-14 16:22 ` Thomas Petazzoni [this message]
2017-03-14 16:39 ` Vicente Olivert Riera
2017-03-14 22:22 ` Thomas Petazzoni
2017-03-15 10:31 ` Vicente Olivert Riera
2017-03-15 12:17 ` Gustavo Zacarias
2017-03-14 20:25 ` Peter Seiderer
2017-03-14 11:46 ` [Buildroot] [PATCH 3/3] libgtk3: bump version to 3.22.10 Vicente Olivert Riera
2017-03-14 22:23 ` Thomas Petazzoni
2017-03-14 22:22 ` [Buildroot] [PATCH 1/3] libgtk3: remove non-existent configure options Thomas Petazzoni
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=20170314172254.367744f2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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