Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 2/6] package/qt6/qt6tools: fix linguist build failure
Date: Sun, 1 Jun 2025 12:38:43 +0200	[thread overview]
Message-ID: <20250601123843.12330c4b@windsurf> (raw)
In-Reply-To: <20250601101305.3198541-3-roykollensvendsen@gmail.com>

Hello Roy,

On Sun,  1 Jun 2025 12:12:56 +0200
Roy Kollen Svendsen <roykollensvendsen@gmail.com> wrote:

> Fixes:
> -- Could NOT find Qt6LinguistTools (missing: Qt6LinguistTools_DIR)
> CMake Error at <...>/output/build/qt6base-6.8.1/cmake/QtToolHelpers.cmake:768 (message):
>   Failed to find the host tool "Qt6::lconvert".  It is part of the
>   Qt6LinguistTools package, but the package could not be found.  Make sure
>   you have built and installed the host Linguist module, which will ensure
>   the creation of the Qt6LinguistTools package.
> Call Stack (most recent call first):
>   <...>/output/build/qt6base-6.8.1/cmake/QtToolHelpers.cmake:83 (qt_internal_find_tool)
>   src/linguist/lconvert/CMakeLists.txt:9 (qt_internal_add_tool)
> 
> The above error can be triggered by the following defconfig:
> BR2_arm=y
> BR2_cortex_a9=y
> BR2_ARM_ENABLE_VFP=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_ARMV7_EABIHF_MUSL_STABLE=y
> BR2_PACKAGE_QT6=y
> BR2_PACKAGE_QT6BASE_GUI=y
> BR2_PACKAGE_QT6BASE_PNG=y
> BR2_PACKAGE_QT6BASE_WIDGETS=y
> BR2_PACKAGE_QT6TOOLS=y
> 
> Signed-off-by: Roy Kollen Svendsen <roykollensvendsen@gmail.com>

Thanks for the new iteration. However is Qt Linguist really a tool that
would be useful on the target? Isn't this a GUI tool used during
development, so something totally useless on the target, and that we
could disable unconditionally?

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

  reply	other threads:[~2025-06-01 10:38 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 [this message]
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
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=20250601123843.12330c4b@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