From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Roy Kollen Svendsen <roykollensvendsen@gmail.com>
Cc: buildroot@buildroot.org, Jesse Van Gavere <jesseevg@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 3/6] package/qt6/qt6tools: fix designer build failure
Date: Sun, 1 Jun 2025 12:39:38 +0200 [thread overview]
Message-ID: <20250601123938.6ceacb39@windsurf> (raw)
In-Reply-To: <20250601101305.3198541-4-roykollensvendsen@gmail.com>
Hello Roy,
On Sun, 1 Jun 2025 12:12:57 +0200
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:
> diff --git a/package/qt6/qt6tools/Config.in b/package/qt6/qt6tools/Config.in
> index 8fff08b3e6..5828715aa6 100644
> --- a/package/qt6/qt6tools/Config.in
> +++ b/package/qt6/qt6tools/Config.in
> @@ -14,6 +14,17 @@ config BR2_PACKAGE_QT6TOOLS
>
> if BR2_PACKAGE_QT6TOOLS
>
> +config BR2_PACKAGE_QT6TOOLS_DESIGNER
> + bool "designer"
> + select BR2_PACKAGE_QT6BASE_GUI # https://code.qt.io/cgit/qt/qttools.git/tree/src/designer/src/designer/CMakeLists.txt?h=6.8.1#n41
> + select BR2_PACKAGE_QT6BASE_NETWORK # https://code.qt.io/cgit/qt/qttools.git/tree/configure.cmake?h=6.8.1#n64
> + select BR2_PACKAGE_QT6BASE_PNG # https://code.qt.io/cgit/qt/qttools.git/tree/configure.cmake?h=6.8.1#n64
> + select BR2_PACKAGE_QT6BASE_WIDGETS # https://code.qt.io/cgit/qt/qttools.git/tree/configure.cmake?h=6.8.1#n64
> + select BR2_PACKAGE_QT6BASE_XML # https://code.qt.io/cgit/qt/qttools.git/tree/src/designer/src/lib/CMakeLists.txt?h=6.8.1#n182
> + help
> + Graphical tool for designing and building Qt user interfaces
> + with a drag-and-drop editor.
Same question about the designer. What would you want to have Qt
Designer on the target, in the context of Buildroot? That you might
want it on the host, why not, but on the target? Or does this option
actually builds it for the host, despite qt6tools being a target
package?
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-06-01 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 10:12 [Buildroot] [PATCH v2 0/6] package/qt6/qt6tools: fix build failures Roy Kollen Svendsen
2025-06-01 10:12 ` [Buildroot] [PATCH v2 1/6] package/qt6/qt6base: add hidden options needed by qt6tools Roy Kollen Svendsen
2025-06-01 10:12 ` [Buildroot] [PATCH v2 2/6] package/qt6/qt6tools: fix linguist build failure Roy Kollen Svendsen
2025-06-01 10:38 ` Thomas Petazzoni via buildroot
2025-06-01 11:18 ` Roy Kollen Svendsen
2025-06-01 10:12 ` [Buildroot] [PATCH v2 3/6] package/qt6/qt6tools: fix designer " Roy Kollen Svendsen
2025-06-01 10:39 ` Thomas Petazzoni via buildroot [this message]
2025-06-01 10:12 ` [Buildroot] [PATCH v2 4/6] package/qt6/qt6tools: fix assistant " Roy Kollen Svendsen
2025-06-01 10:40 ` Thomas Petazzoni via buildroot
2025-06-01 10:12 ` [Buildroot] [PATCH v2 5/6] " Roy Kollen Svendsen
2025-06-01 10:13 ` [Buildroot] [PATCH v2 6/6] package/qt6/qt6tools: build without clang support 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=20250601123938.6ceacb39@windsurf \
--to=buildroot@buildroot.org \
--cc=jesseevg@gmail.com \
--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