From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/qt5/qt5charts: fix install with per-package
Date: Mon, 17 Feb 2020 01:13:57 +0100 [thread overview]
Message-ID: <20200217011357.2c7d1f95@windsurf> (raw)
In-Reply-To: <CAPi7W80D9eZJDs-0N+5SA1Z5PGJB-1hvn6h1Dz=aWW=SfSGKMQ@mail.gmail.com>
Hello,
On Sun, 16 Feb 2020 22:03:48 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> > The original 'libQt5Charts.so.2.1.3' file is installed into the qt5base per-package directory instead
> > of the qt5charts per-package directory one...
> Indeed, you're right, I thought my patch was fixing the issue but it
> was not. The issue was fixed by running make qt5charts-dirclean and
> make qt5charts a second time ...
> It should be noted that the same kind of build failure are raised on
> qt5svg, qt5webengine, qt5xmlpatterns and qt5scripts.
> There is patch in patchwork from March 2019 that could fix this issue
> but it is set as superseded:
> https://patchwork.ozlabs.org/patch/1056425/.
Andreas Naumann (in Cc) is working on making Qt5 compatible with
per-package directory builds.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-17 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 19:42 [Buildroot] [PATCH 1/1] package/qt5/qt5charts: fix install with per-package Fabrice Fontaine
2020-02-16 20:23 ` Peter Seiderer
2020-02-16 21:03 ` Fabrice Fontaine
2020-02-17 0:13 ` Thomas Petazzoni [this message]
2020-02-17 19:19 ` Andreas Naumann
2020-02-17 19:25 ` Thomas Petazzoni
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=20200217011357.2c7d1f95@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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