From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 3/3] qt5base: make harfbuzz support selectable
Date: Mon, 20 Feb 2017 22:22:12 +0100 [thread overview]
Message-ID: <20170220222212.458f5c7d@free-electrons.com> (raw)
In-Reply-To: <20170220221444.4792d09a@gmx.net>
Hello,
On Mon, 20 Feb 2017 22:14:44 +0100, Peter Seiderer wrote:
> This patch is a follow up on your (and Arnout's) suggestion to prefer
> system libraries, freetype first, harzbuzz second..., so logically it
> belongs to the freetype patch...
>
> But no mandatory need for this patch to be applied to master, maybe
> next is enough...
>
> At the moment always the qt built-in harfbuzz is used...
OK. The freetype one was really needed in master as it was fixing a
build issue.
However, I'll keep the harfbuzz patch around until next gets merged
back into master after the release. We've been building Qt with the
internal harfbuzz so far, so let's keep it this way for the release.
Are you also looking at the other qt5 failures on various
architectures?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-20 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 11:32 [Buildroot] [PATCH v3 1/3] qt5base: move linuxfb configure option comment Peter Seiderer
2017-02-18 11:32 ` [Buildroot] [PATCH v3 2/3] qt5base: use system/buildroot provided freetype Peter Seiderer
2017-02-20 21:04 ` Thomas Petazzoni
2017-02-18 11:32 ` [Buildroot] [PATCH v3 3/3] qt5base: make harfbuzz support selectable Peter Seiderer
2017-02-20 21:04 ` Thomas Petazzoni
2017-02-20 21:14 ` Peter Seiderer
2017-02-20 21:22 ` Thomas Petazzoni [this message]
2017-04-08 14:09 ` Thomas Petazzoni
2017-04-09 19:32 ` Peter Seiderer
2017-10-21 19:38 ` Arnout Vandecappelle
2017-02-20 21:04 ` [Buildroot] [PATCH v3 1/3] qt5base: move linuxfb configure option comment 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=20170220222212.458f5c7d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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