From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/qt6/qt6quicktimeline: add missing select BR2_PACKAGE_QT6DECLARATIVE
Date: Mon, 6 Jan 2025 23:19:54 +0100 [thread overview]
Message-ID: <20250106231954.734c2006@windsurf> (raw)
In-Reply-To: <CA+R_deqLs+aSCBvoTGj9rJn8D5ARu1=QFKDy19qgTP_YWBdU0g@mail.gmail.com>
Hello Roy,
On Mon, 6 Jan 2025 23:07:46 +0100
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:
> How can I recreate the warning reported by kconfig?
Like this:
$ cat > .config <<EOF
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_VFP=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
BR2_PACKAGE_QT6=y
BR2_PACKAGE_QT6QUICKTIMELINE=y
EOF
$ make olddefconfig
WARNING: unmet direct dependencies detected for BR2_PACKAGE_QT6DECLARATIVE_QUICK
Depends on [n]: BR2_PACKAGE_QT6 [=y] && BR2_PACKAGE_QT6DECLARATIVE [=n]
Selected by [y]:
- BR2_PACKAGE_QT6QUICKTIMELINE [=y] && BR2_PACKAGE_QT6 [=y]
#
# configuration written to /home/thomas/projets/buildroot/.config
#
Basically, just enable qt6 and qt6quicktimeline. You can even do it
from menuconfig, and then when you exit menuconfig, you will see the
kconfig warning.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-06 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 21:06 [Buildroot] [PATCH] package/qt6/qt6quicktimeline: add missing select BR2_PACKAGE_QT6DECLARATIVE Thomas Petazzoni via buildroot
[not found] ` <CA+R_deqLs+aSCBvoTGj9rJn8D5ARu1=QFKDy19qgTP_YWBdU0g@mail.gmail.com>
2025-01-06 22:19 ` Thomas Petazzoni via buildroot [this message]
2025-01-07 7:01 ` Roy Kollen Svendsen
2025-01-06 22:33 ` Julien Olivain
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=20250106231954.734c2006@windsurf \
--to=buildroot@buildroot.org \
--cc=roykollensvendsen@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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