All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/3] package/waffle: new package
Date: Sat, 22 Sep 2018 14:46:18 +0200	[thread overview]
Message-ID: <20180922144618.5e85cf9f@windsurf> (raw)
In-Reply-To: <20180922105626.22626-2-romain.naour@gmail.com>

Hello,

On Sat, 22 Sep 2018 12:56:25 +0200, Romain Naour wrote:

> +config BR2_PACKAGE_WAFFLE
> +	bool "waffle"
> +	depends on BR2_PACKAGE_WAFFLE_SUPPORTS_GLX || \
> +		BR2_PACKAGE_WAFFLE_SUPPORTS_WAYLAND || \
> +		BR2_PACKAGE_WAFFLE_SUPPORTS_X11_EGL || \
> +		BR2_PACKAGE_WAFFLE_SUPPORTS_GBM
> +	depends on BR2_PACKAGE_HAS_LIBGLES # dlopen'ing the GLES libararies at runtime.

Are you sure that GLES support *must* be available ?

This seems very weird, because in a typical "desktop" context, with
X.org and GLX, you have full OpenGL support, but you don't have GLES
libraries available.

Is this dependency coming from actual runtime issues you have
encountered ? Could you explain it in a bit more details ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-09-22 12:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-22 10:56 [Buildroot] [PATCH v3 1/3] package/python-numpy: add host variant for piglit Romain Naour
2018-09-22 10:56 ` [Buildroot] [PATCH v3 2/3] package/waffle: new package Romain Naour
2018-09-22 12:46   ` Thomas Petazzoni [this message]
2018-09-22 18:15     ` Romain Naour
2018-10-09 20:01   ` Thomas Petazzoni
2018-09-22 10:56 ` [Buildroot] [PATCH v3 3/3] package/piglit: " Romain Naour
2019-01-01 19:57   ` Romain Naour
2018-10-09 20:00 ` [Buildroot] [PATCH v3 1/3] package/python-numpy: add host variant for piglit 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=20180922144618.5e85cf9f@windsurf \
    --to=thomas.petazzoni@bootlin.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.