From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Qwt package : added dependency to Qt5 besides Qt.
Date: Sun, 24 Jan 2016 17:20:41 +0100 [thread overview]
Message-ID: <20160124162041.GF3405@free.fr> (raw)
In-Reply-To: <56A4244D.3090504@mind.be>
David, Arnout, All,
On 2016-01-24 02:09 +0100, Arnout Vandecappelle spake thusly:
> On 22-01-16 19:19, Yann E. MORIN wrote:
> > David, All,
> >
> > On 2016-01-22 18:44 +0100, David Picard spake thusly:
> [snip]
> >> @@ -21,10 +23,14 @@ config BR2_PACKAGE_QWT_OPENGL
> >> bool "OpenGL support"
> >> depends on BR2_PACKAGE_HAS_LIBGLES
> >> depends on BR2_PACKAGE_HAS_LIBEGL
> >> - select BR2_PACKAGE_QT_OPENGL_ES
> >> + select BR2_PACKAGE_QT_OPENGL_ES if BR2_PACKAGE_QT
> >> + select BR2_PACKAGE_QT5BASE_OPENGL_LIB if BR2_PACKAGE_QT5BASE
> >
> > BR2_PACKAGE_QT5BASE_OPENGL_LIB depends on BR2_PACKAGE_QT5BASE_OPENGL, so
> > it should have been selected too.
> >
> > However, I'm a bit worried about the complexity here, and I'd rather
> > that we depend on such support rather than select it. So I'd prefer to
> > see:
> >
> > depends on BR2_PACKAGE_QT_OPENGL_ES || BR2_PACKAGE_QT5BASE_OPENGL_LIB
>
> In that case, it can probably be removed completely and turned into an
> automatic dependency (i.e. just in the .mk file).
>
> I also wouldn't bother with legacy handling when this symbol is removed. The
> legacy .config file will already contain BR2_PACKAGE_QT_OPENGL_ES, so once the
> handling is automatic, you just have to run 'make oldconfig' and it will Just
> Work (TM).
Yes, an automatic dependency in the .mk would be perfectly enough, I
guess.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-01-24 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 17:44 [Buildroot] [PATCH 1/2] Update for 2015.11.1 David Picard
2016-01-22 17:44 ` [Buildroot] [PATCH 2/2] Qwt package : added dependency to Qt5 besides Qt David Picard
2016-01-22 18:19 ` Yann E. MORIN
[not found] ` <56A34AFC.7070908@yahoo.fr>
2016-01-23 13:32 ` Yann E. MORIN
2016-01-24 1:09 ` Arnout Vandecappelle
2016-01-24 16:20 ` Yann E. MORIN [this message]
2016-01-25 9:13 ` David Picard
2016-01-25 9:25 ` David Picard
2016-01-25 14:40 ` David Picard
2016-01-22 17:50 ` [Buildroot] [PATCH 1/2] Update for 2015.11.1 Yann E. MORIN
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=20160124162041.GF3405@free.fr \
--to=yann.morin.1998@free.fr \
--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