From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libv4l: qv4l2 doesn't support GLES
Date: Mon, 19 Mar 2018 18:04:50 +0100 [thread overview]
Message-ID: <20180319180450.14dd21d9@gmx.net> (raw)
In-Reply-To: <20180319105531.34918-1-phil@zankapfel.net>
Hello Phil,
On Mon, 19 Mar 2018 11:55:31 +0100, Phil Eichinger <phil@zankapfel.net> wrote:
> qv4l2 explicitly sets QT_NO_OPENGL_ES_2 because GLES is not supported
> yet. So compiling with Qt5 which has only GLES enabled fails.
>
> https://git.linuxtv.org/v4l-utils.git/commit/utils/qv4l2?id=c185420d494d8985ec3aab6b2a28f858046052b5
> Signed-off-by: Phil Eichinger <phil@zankapfel.net>
> ---
> package/libv4l/libv4l.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/libv4l/libv4l.mk b/package/libv4l/libv4l.mk
> index 11061306c7..5eb26ee16c 100644
> --- a/package/libv4l/libv4l.mk
> +++ b/package/libv4l/libv4l.mk
> @@ -51,7 +51,7 @@ endif
> ifeq ($(BR2_PACKAGE_LIBV4L_UTILS),y)
> LIBV4L_CONF_OPTS += --enable-v4l-utils
> LIBV4L_DEPENDENCIES += $(TARGET_NLS_DEPENDENCIES)
> -ifeq ($(BR2_PACKAGE_QT5BASE)$(BR2_PACKAGE_QT5BASE_GUI)$(BR2_PACKAGE_QT5BASE_WIDGETS),yyy)
> +ifeq ($(BR2_PACKAGE_QT5BASE)$(BR2_PACKAGE_QT5BASE_GUI)$(BR2_PACKAGE_QT5BASE_WIDGETS)$(BR2_PACKAGE_QT5BASE_OPENGL_DESKTOP),yyyy)
NAK, qv4l2 builds just fine with framebuffer/widgets support, see libv4l-1.14.1/config.h
HAVE_QTGL configure logic and libv4l-1.14.1/utils/qv4l2/* conditional compile logic...
Do your have a (minimal) buildroot defconfig which failes to build libv4l?
Regards,
Peter
> LIBV4L_CONF_OPTS += --enable-qv4l2
> LIBV4L_DEPENDENCIES += qt5base
> # protect against host version detection of moc-qt5/rcc-qt5/uic-qt5
next prev parent reply other threads:[~2018-03-19 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 10:55 [Buildroot] [PATCH 1/1] libv4l: qv4l2 doesn't support GLES Phil Eichinger
2018-03-19 17:04 ` Peter Seiderer [this message]
2018-03-20 8:41 ` phil eichinger
2018-03-20 9:42 ` Peter Seiderer
2018-10-20 19:00 ` 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=20180319180450.14dd21d9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox