From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] package/qt5webengine: examples need qt5svg
Date: Tue, 11 Aug 2020 21:28:52 +0200 [thread overview]
Message-ID: <20200811212852.387f7769@windsurf.home> (raw)
In-Reply-To: <20200811203155.76632009@gmx.net>
Hello,
+Yann in Cc for Kconfig expertise.
On Tue, 11 Aug 2020 20:31:55 +0200
Peter Seiderer <ps.report@gmx.net> wrote:
> package/qt5/qt5base/Config.in:1:error: recursive dependency detected!
> package/qt5/qt5base/Config.in:1: symbol BR2_PACKAGE_QT5BASE is selected by BR2_PACKAGE_QT5SVG
Right, this makes sense.
> package/qt5/qt5svg/Config.in:1: symbol BR2_PACKAGE_QT5SVG is selected by BR2_PACKAGE_QT5BASE_EXAMPLES
This doesn't make any sense to me:
config BR2_PACKAGE_QT5BASE_EXAMPLES
bool "Compile and install examples (with code)"
select BR2_PACKAGE_QT5BASE_NETWORK
select BR2_PACKAGE_QT5BASE_XML
help
If unsure, say N.
Neither BR2_PACKAGE_QT5BASE_NETWORK nor BR2_PACKAGE_QT5BASE_XML are
selecting BR2_PACKAGE_QT5SVG.
Or perhaps it is the line added by your patch:
select BR2_PACKAGE_QT5SVG if BR2_PACKAGE_QT5BASE_EXAMPLES
which causes this statement ?
> package/qt5/qt5base/Config.in:42: symbol BR2_PACKAGE_QT5BASE_EXAMPLES depends on BR2_PACKAGE_QT5BASE
This obviously makes sense.
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
>
> Regards,
> Peter
>
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-08-11 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 20:38 [Buildroot] [PATCH v1] package/qt5webengine: examples need qt5svg Peter Seiderer
2020-08-11 18:31 ` Peter Seiderer
2020-08-11 19:28 ` Thomas Petazzoni [this message]
2020-08-11 21:26 ` Peter Seiderer
2020-08-11 21:33 ` 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=20200811212852.387f7769@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 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.