buildroot.busybox.net archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Ivan Castell <icastell@circontrol.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Missing support of libsvg with qt6
Date: Tue, 14 Mar 2023 22:20:29 +0100	[thread overview]
Message-ID: <20230314222029.1c818de0@windsurf> (raw)
In-Reply-To: <DB4PR05MB103906C9B5FCFAEBE1B0FBF8CA3BE9@DB4PR05MB10390.eurprd05.prod.outlook.com>

Hello Ivan,

On Tue, 14 Mar 2023 13:03:01 +0000
Ivan Castell <icastell@circontrol.com> wrote:

> We are using buildroot-2022.11.1 to build a custom QT6 based project. We have this option enabled in menuconfig:
> 
> BR2_PACKAGE_QT6=y
> 
> But found this issue building our project:
> 
> Project ERROR: Unknown module(s) in QT: svgwidgets
>
> It seems there is no way to enable SVG library support on QT6 (at least we don't found it). However, SVG library is completely ported and functional using Qt5.
> 
> BR2_PACKAGE_QT5SVG=y
> 
> Does buildroot will support SVG library with QT6 in some future release? Is this still a work in progress? We have checked buildroot-2023.02 and even in that recent version, is still not ready.

At this point, nobody has worked on packaging qt6svg. However, taking
example on qt6serialbus or qt6serialport, it should be relatively easy.
Perhaps you could give it a try and submit a patch? This would
certainly be welcome!

Best regards,

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:[~2023-03-14 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 13:03 [Buildroot] Missing support of libsvg with qt6 Ivan Castell
2023-03-14 21:20 ` Thomas Petazzoni via buildroot [this message]
2023-03-19 10:18   ` Peter Seiderer

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=20230314222029.1c818de0@windsurf \
    --to=buildroot@buildroot.org \
    --cc=icastell@circontrol.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;
as well as URLs for NNTP newsgroup(s).