Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/qwt: needs qt5base gui support
Date: Fri, 15 Feb 2019 21:43:43 +0100	[thread overview]
Message-ID: <20190215214343.68c0b057@windsurf.home> (raw)
In-Reply-To: <20190215202504.24205-1-ps.report@gmx.net>

Hello Peter,

On Fri, 15 Feb 2019 21:25:04 +0100
Peter Seiderer <ps.report@gmx.net> wrote:

> Fixes the following qt5base configure error ([1]):
> 
>   ERROR: Feature 'widgets' was enabled, but the pre-condition 'features.gui' failed.
> 
> [1] http://autobuild.buildroot.net/results/c771c2d5aac3e21f908e5a118f3755dbc9301a47
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
>  package/qwt/Config.in | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/package/qwt/Config.in b/package/qwt/Config.in
> index f4132c8638..2e9cec19d7 100644
> --- a/package/qwt/Config.in
> +++ b/package/qwt/Config.in
> @@ -2,6 +2,7 @@ config BR2_PACKAGE_QWT
>  	bool "qwt"
>  	depends on BR2_PACKAGE_QT5
>  	select BR2_PACKAGE_QT5BASE
> +	select BR2_PACKAGE_QT5BASE_GUI

Hm, the build error happens in qt5base, and to me reads as "if you have
widgets support enabled in qt5base, you must have gui support enabled
in qt5base". If that is what is happening, then what you want to do is
have BR2_PACKAGE_QT5BASE_WIDGETS sleect BR2_PACKAGE_QT5BASE_GUI, and
not touch qwt.

Indeed, to me, it seems like any other package that uses qt5 widgets
without selecting qt5 gui would fall into the same build failure.

Also, any idea why this is popping up only now ?

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

  reply	other threads:[~2019-02-15 20:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 20:25 [Buildroot] [PATCH v1] package/qwt: needs qt5base gui support Peter Seiderer
2019-02-15 20:43 ` Thomas Petazzoni [this message]
2019-02-15 20:58   ` Peter Seiderer
2019-02-15 21:40     ` Thomas Petazzoni
2019-02-22 11:44       ` Peter Korsgaard

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=20190215214343.68c0b057@windsurf.home \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox