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 23:22:56 +0100 [thread overview]
Message-ID: <20170314232256.4dfd5f7d@free-electrons.com> (raw)
In-Reply-To: <0778ff37-bb18-3b1b-3666-77ca979a9958@imgtec.com>
Hello,
On Tue, 14 Mar 2017 16:39:04 +0000, Vicente Olivert Riera wrote:
> > 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?
>
> maybe the gdk-wayland backend is necessary to run gtk3 apps on a Wayland
> display server, but it still needs some libX11 bits because the support
> is not complete. Just guessing :P
With which OpenGL ES/EGL provider did you get this build failure?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-14 22: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
2017-03-14 16:39 ` Vicente Olivert Riera
2017-03-14 22:22 ` Thomas Petazzoni [this message]
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=20170314232256.4dfd5f7d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.