From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>,
Simon Ruepp <ruepp.simon@mailbox.org>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Julien Corjon <corjon.j@ecagroup.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2] package/qt5/qt53d: fix compilation error
Date: Fri, 2 Aug 2024 19:18:07 +0200 [thread overview]
Message-ID: <20240802191807.1b4edf36@windsurf> (raw)
In-Reply-To: <20240724222144.00bffdf2@windsurf>
Hello Simon,
Gentle ping on the below questions, in order to be able to move forward
with resolving this qt53d build issue.
Thanks a lot for your contribution!
Thomas
On Wed, 24 Jul 2024 22:21:44 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> Hello Simon,
>
> On Wed, 24 Jul 2024 10:54:44 +0200
> Simon Ruepp via buildroot <buildroot@buildroot.org> wrote:
>
> > Compiling the qt53d package currently fails since the required
> > source files of the assimp library are missing. Because of this,
> > QT53D_EXTRA_DOWNLOADS along with a post extract hook is used
> > to separately download and extract the missing files.
> >
> > Signed-off-by: Simon Ruepp <ruepp.simon@mailbox.org>
>
> Thanks for the patch. Could you document since when this is failing,
> i.e which Buildroot commit introduced this regression?
>
> Also, could you comment on how this will interact with:
>
> ifeq ($(BR2_PACKAGE_ASSIMP),y)
> QT53D_DEPENDENCIES += assimp
> endif
>
> that we have in qt53.mk. It seems like qt53d can use a system-provided
> assimp instead of a bundled copy of assimp:
>
> !ios:!tvos:!qcc:qtConfig(assimp):if(qtConfig(system-assimp)|android-clang|clang|win32-msvc|gcc) {
> SUBDIRS += assimp
> }
>
> (from src/plugins/sceneparsers/sceneparsers.pro). There is apparently a
> -assimp config option that allows to chose between "system", "qt" and
> "no".
>
> Also, I see that src/3rdparty/patches/ has a bunch of patches for
> assimp. Should these patches be applied? Are they important?
>
> Thanks a lot for your additional investigations :-)
>
> 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-08-02 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 10:32 [Buildroot] [PATCH 1/1] package/qt5/qt53d: fix compilation error Simon Ruepp via buildroot
2024-07-23 12:27 ` Thomas Petazzoni via buildroot
2024-07-24 8:54 ` [Buildroot] [PATCH v2] " Simon Ruepp via buildroot
2024-07-24 20:21 ` Thomas Petazzoni via buildroot
2024-08-02 17:18 ` Thomas Petazzoni via buildroot [this message]
2024-08-04 9:12 ` Simon Ruepp via buildroot
2024-09-13 9:26 ` Simon Ruepp via buildroot
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=20240802191807.1b4edf36@windsurf \
--to=buildroot@buildroot.org \
--cc=corjon.j@ecagroup.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=ruepp.simon@mailbox.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.