From: Peter Seiderer <ps.report@gmx.net>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: "Arthur Courtel" <arthur.courtel@smile.fr>,
"Mahyar Koshkouei" <mahyar.koshkouei@gmail.com>,
"Gaël Portay" <gael.portay@collabora.com>,
"Julien Corjon" <corjon.j@ecagroup.com>,
buildroot@busybox.net, "Martin Bark" <martin@barkynet.com>,
"Maxime Hadjinlian" <maxime.hadjinlian@gmail.com>
Subject: Re: [Buildroot] [PATCH v1] package/qt5webengine: add optional host-freetype/host-libjpeg dependency
Date: Sun, 16 Jan 2022 00:04:35 +0100 [thread overview]
Message-ID: <20220116000435.03d5b920@gmx.net> (raw)
In-Reply-To: <20220109144430.1064ea1c@windsurf>
Hello Thomas,
On Sun, 9 Jan 2022 14:44:30 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Sun, 9 Jan 2022 14:27:48 +0100
> Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
>
> > I am falling into this issue while building the following defconfig:
> >
> > BR2_arm=y
> > BR2_arm1176jzf_s=y
> > BR2_TOOLCHAIN_EXTERNAL=y
> > BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
> > BR2_PACKAGE_QT5=y
> > BR2_PACKAGE_QT5WEBENGINE=y
> > BR2_PACKAGE_RPI_USERLAND=y
> >
> > Did you had the chance to investigate more deeply why having fontconfig
> > support in Qt leads qt5webengine wanting to find freetype2 on the host?
>
> Interestingly, in commit
> https://github.com/meta-qt5/meta-qt5/commit/280487f20bca829527a597d6263b0344a01917ac#diff-f0ffde666f6ff0282f8400203b3ba20968494d3c7245106eca761bd79baa1c78R26
> the meta-qt5 layer, when upgrading Qt to 5.15.2 added jpeg-native and
> freetype-native as new unconditional dependencies.
>
> But there are no explanations. Is it really because the Chromium stuff
> is building a host tool with freetype/jpeg, or is it just a workaround
> for some incorrect behavior of the Chromium build process that needs
> freetype/jpeg on the target, but checks for them on the host?
Would say yes...
Regards,
Peter
>
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-15 23:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 20:39 [Buildroot] [PATCH v1 0/2] Raspberry Pi - bump kernel version to 967d45b (5.10.1) Peter Seiderer
2020-12-21 20:39 ` [Buildroot] [PATCH v1 1/2] configs/raspberrypi*: " Peter Seiderer
2020-12-22 18:51 ` Marcin Niestrój
2020-12-23 9:12 ` Peter Korsgaard
2020-12-21 20:39 ` [Buildroot] [PATCH v1] package/qt5webengine: add optional host-freetype/host-libjpeg dependency Peter Seiderer
2020-12-30 10:18 ` Thomas Petazzoni
2021-01-19 21:22 ` Thomas Petazzoni
2021-01-21 21:03 ` Peter Seiderer
2021-01-21 21:09 ` Thomas Petazzoni
2022-01-09 13:27 ` Thomas Petazzoni
2022-01-09 13:44 ` Thomas Petazzoni
2022-01-15 23:04 ` Peter Seiderer [this message]
2022-01-15 23:03 ` Peter Seiderer
2022-01-16 10:38 ` James Hilliard
2020-12-21 20:39 ` [Buildroot] [PATCH v1 2/2] package/rpi-firmware: bump version to d016a6e Peter Seiderer
2020-12-22 18:52 ` Marcin Niestrój
2020-12-23 9:12 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2020-12-20 14:57 [Buildroot] [PATCH v1] package/qt5webengine: add optional host-freetype/host-libjpeg dependency 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=20220116000435.03d5b920@gmx.net \
--to=ps.report@gmx.net \
--cc=arthur.courtel@smile.fr \
--cc=buildroot@busybox.net \
--cc=corjon.j@ecagroup.com \
--cc=gael.portay@collabora.com \
--cc=mahyar.koshkouei@gmail.com \
--cc=martin@barkynet.com \
--cc=maxime.hadjinlian@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