From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Roy Kollen Svendsen <roy.kollen.svendsen@akersolutions.com>,
Samuel Martin <s.martin49@gmail.com>,
Roy Kollen Svendsen <roykollensvendsen@gmail.com>,
buildroot@buildroot.org, Zoltan Gyarmati <zgyarmati@zgyarmati.de>,
Romain Naour <romain.naour@smile.fr>,
Jesse Van Gavere <jesseevg@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 03/11] package/qt6/qt6shadertools: new package
Date: Thu, 9 May 2024 22:43:37 +0200 [thread overview]
Message-ID: <20240509224337.253b2bde@windsurf> (raw)
In-Reply-To: <Zj00B8A-pgDg5rvn@landeda>
Hello,
On Thu, 9 May 2024 22:37:27 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> We have a few other host packages that have a no-prompt boolean option,
> like dracut, eudev, patchelf, systemd.
>
> The converse is non-existent; we only have ARCH_SUPPORTS for a few host
> packages for languages:
>
> $ git grep -E 'config BR2_PACKAGE_HOST_' -- '*/Config.in'
> package/erlang/Config.in:config BR2_PACKAGE_HOST_ERLANG_ARCH_SUPPORTS
> package/mono/Config.in:config BR2_PACKAGE_HOST_MONO_ARCH_SUPPORTS
> package/openjdk/Config.in:config BR2_PACKAGE_HOST_OPENJDK_BIN_ARCH_SUPPORTS
> package/protobuf/Config.in:config BR2_PACKAGE_HOST_PROTOBUF_ARCH_SUPPORTS
>
> So, yes, I'd rather have BR2_PACKAGE_HOST_QT6BASE_GUI in its own
> Config.in.host.
ACK.
> Also, it is a bit weird that this is an option for a host package
> without a kconfig symbol for the host package itself...
I don't find it weird. We need host-qt6base with some specific
features (which we don't want to build in all cases, as it takes time),
but really host-qt6base doesn't have to be user-visible in menuconfig,
as it's merely a build dependency.
> Also, adding the support for GUI in host qt6base should be in its own
> patch, separate from the one introducing qt6shadertools.
Agreed.
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:[~2024-05-09 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:05 [Buildroot] [PATCH v2 01/11] package/qt6: bump version to 6.7.0 Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 02/11] package/qt6base: avoid enabling both desktop and es2 opengl Roy Kollen Svendsen
2024-05-09 14:42 ` Thomas Petazzoni via buildroot
2024-05-10 7:56 ` Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 03/11] package/qt6/qt6shadertools: new package Roy Kollen Svendsen
2024-05-09 14:45 ` Thomas Petazzoni via buildroot
2024-05-09 20:37 ` Yann E. MORIN
2024-05-09 20:43 ` Thomas Petazzoni via buildroot [this message]
2024-05-09 20:49 ` Arnout Vandecappelle via buildroot
2024-05-09 20:58 ` Jesse Van Gavere
2024-04-17 8:05 ` [Buildroot] [PATCH v2 04/11] package/qt6/qt6svg: allow building for host Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 05/11] package/qt6/qt6languageserver: new package Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 06/11] package/qt6/qt6declarative: " Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 07/11] package/qt6/qt6websockets: " Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 08/11] package/qt6/qt6wayland: " Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 09/11] package/qt6/qt6tools: " Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 10/11] package/qt6/qt6virtualkeyboard: " Roy Kollen Svendsen
2024-04-17 8:05 ` [Buildroot] [PATCH v2 11/11] package/qt6/qt6mqtt: " Roy Kollen Svendsen
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=20240509224337.253b2bde@windsurf \
--to=buildroot@buildroot.org \
--cc=jesseevg@gmail.com \
--cc=romain.naour@smile.fr \
--cc=roy.kollen.svendsen@akersolutions.com \
--cc=roykollensvendsen@gmail.com \
--cc=s.martin49@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
--cc=zgyarmati@zgyarmati.de \
/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