From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/4] libv4l: bump version to 1.8.0
Date: Sun, 11 Oct 2015 23:41:45 +0200 [thread overview]
Message-ID: <20151011234145.79585714@gmx.net> (raw)
In-Reply-To: <20151010115242.12c4d02e@free-electrons.com>
Hello Thomas,
On Sat, 10 Oct 2015 11:52:42 +0200, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Dear Peter Seiderer,
>
> On Wed, 7 Oct 2015 23:56:50 +0200, Peter Seiderer wrote:
>
> > ifeq ($(BR2_PACKAGE_LIBV4L_UTILS),y)
> > +ifneq ($(BR2_PACKAGE_QT5BASE)$(BR2_PACKAGE_QT),)
> > +LIBV4L_DEPENDENCIES += $(if $(BR2_PACKAGE_QT5BASE),qt5base,qt)
>
> This doesn't seem quite right for Qt5. According to the configure.ac,
> much more than qt5base is needed:
>
> PKG_CHECK_MODULES(QT5, [Qt5Core >= 5.0 Qt5Gui >= 5.0 Qt5Widgets >= 5.0], [qt_pkgconfig=true], [qt_pkgconfig=false])
>
> So it looks like that for Qt5, we need to depend on qt5base, qt5gui and
> qt5widgets. Note that it can also depend on Qt5OpenGL:
>
> PKG_CHECK_MODULES(QT5GL, [Qt5OpenGL >= 5.0 gl], [qt_pkgconfig_gl=true], [qt_pkgconfig_gl=false])
>
Yes, you are right...
> So maybe we need an explicit option to enable Qt support in libv4l,
> sometihng like (I haven't checked all Config.in options, so do not
> copy/paste the below) :
>
> config BR2_PACKAGE_LIBV4L_UTILS_QT
> bool "qt-based tools"
> depends on BR2_PACKAGE_QT || BR2_PACKAGE_QT5
> select BR2_PACKAGE_QT5BASE if BR2_PACKAGE_QT5
> select BR2_PACKAGE_QT5GUI if BR2_PACKAGE_QT5
> select BR2_PACKAGE_QT5WIDGETS if BR2_PACKAGE_QT5
> select BR2_PACKAGE_QT_<something> if BR2_PACKAGE_QT
>
> and then, in the .mk file:
>
> ifeq ($(BR2_PACKAGE_LIBV4L_UTILS_QT),y)
> ifeq ($(BR2_PACKAGE_QT),y)
> LIBV4L_DEPENDENCIES += qt
> else ifeq ($(BR2_PACKAGE_QT5),y)
> LIBV4L_DEPENDENCIES += qt5base qt5gui qt5widgets
> ifeq ($(BR2_PACKAGE_QT5OPENGL),y)
> LIBV4L_DEPENDENCIES += qt5opengl
> endif
> endif
>
> Or, alternatively, if you don't want to add a new Config.in option,
> then you should improve the .mk file logic with all the proper
> dependencies.
>
O.k. will cook up a follow up patch...
Regards,
Peter
> Best regards,
>
> Thomas
next prev parent reply other threads:[~2015-10-11 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 21:56 [Buildroot] [PATCH v2 1/4] libv4l: update v4l-utils help text (add more listed tools) Peter Seiderer
2015-10-07 21:56 ` [Buildroot] [PATCH v2 2/4] media-ctl: remove package Peter Seiderer
2015-10-10 9:47 ` Thomas Petazzoni
2015-10-07 21:56 ` [Buildroot] [PATCH v2 3/4] Config.in.legacy: add missing select BR2_LEGACY Peter Seiderer
2015-10-07 23:11 ` Gustavo Zacarias
2015-10-09 13:28 ` Thomas Petazzoni
2015-10-09 13:32 ` Thomas Petazzoni
2015-10-09 21:06 ` Peter Seiderer
2015-10-07 21:56 ` [Buildroot] [PATCH v2 4/4] libv4l: bump version to 1.8.0 Peter Seiderer
2015-10-10 9:52 ` Thomas Petazzoni
2015-10-11 21:41 ` Peter Seiderer [this message]
2015-10-10 9:46 ` [Buildroot] [PATCH v2 1/4] libv4l: update v4l-utils help text (add more listed tools) 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=20151011234145.79585714@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