All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] libgtk3: gdk-wayland backend depends on libX11
Date: Tue, 14 Mar 2017 21:25:44 +0100	[thread overview]
Message-ID: <20170314212544.59e4eb22@gmx.net> (raw)
In-Reply-To: <20170314114628.10147-2-Vincent.Riera@imgtec.com>

Hello Vicente,

On Tue, 14 Mar 2017 11:46:27 +0000, Vicente Olivert Riera <Vincent.Riera@imgtec.com> wrote:

> Otherwise it will fail to compile with an error like this one:
> 
> [Vincent: paths shortened for readability]
> 
>   CC       gdkglcontext-wayland.lo
> In file included from /usr/include/epoxy/egl_generated.h:11:0,
>                  from /usr/include/epoxy/egl.h:44,
>                  from gdkglcontext-wayland.h:32,
>                  from gdkglcontext-wayland.c:24:
> /usr/include/EGL/eglplatform.h:119:22: fatal error: X11/Xlib.h: No such
> file or directory
>  #include <X11/Xlib.h>
>                       ^
> compilation terminated.
> make[6]: *** [Makefile:682: gdkglcontext-wayland.lo] Error 1
> 

Qt has a similare build failure solved by -DQT_EGL_NO_X11 which is used by
qt5base-5.8.0/src/platformsupport/eglconvenience/qt_egl_p.h:

#ifdef QT_EGL_NO_X11
# define MESA_EGL_NO_X11_HEADERS // MESA
# define WIN_INTERFACE_CUSTOM    // NV
#endif // QT_EGL_NO_X11

#ifdef QT_EGL_WAYLAND
# define WAYLAND // NV
#endif // QT_EGL_WAYLAND

#include <EGL/egl.h>
#include <EGL/eglext.h>

Maybe something similare (define MESA_EGL_NO_X11_HEADERS) works for
the gdk-wayland backend?

Regards,
Peter


> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
>  package/libgtk3/Config.in | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/package/libgtk3/Config.in b/package/libgtk3/Config.in
> index 738f865..9e0721d 100644
> --- a/package/libgtk3/Config.in
> +++ b/package/libgtk3/Config.in
> @@ -62,11 +62,15 @@ comment "Wayland GDK backend needs an OpenGL EGL backend provided by mesa3d w/ h
>  	depends on !BR2_PACKAGE_MESA3D_OPENGL_EGL || \
>  		!BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_17
>  
> +comment "Wayland GDK backend needs libX11 support"
> +	depends on !BR2_PACKAGE_XLIB_LIBX11
> +
>  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
>  	select BR2_PACKAGE_WAYLAND
>  	select BR2_PACKAGE_WAYLAND_PROTOCOLS
>  	select BR2_PACKAGE_LIBXKBCOMMON

  parent reply	other threads:[~2017-03-14 20:25 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
2017-03-15 10:31         ` Vicente Olivert Riera
2017-03-15 12:17           ` Gustavo Zacarias
2017-03-14 20:25   ` Peter Seiderer [this message]
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=20170314212544.59e4eb22@gmx.net \
    --to=ps.report@gmx.net \
    --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.