From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/2] qt5base: use system/buildroot provided freetype
Date: Fri, 10 Feb 2017 15:36:19 +0100 [thread overview]
Message-ID: <20170210153619.2d894fa5@gmx.net> (raw)
In-Reply-To: <20170210093634.68f43e26@free-electrons.com>
Hello Thomas,
On Fri, 10 Feb 2017 09:36:34 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Thu, 9 Feb 2017 23:30:54 +0100, Peter Seiderer wrote:
> > Fixes [1]:
> >
> > Project ERROR: Library 'libpng' is not defined.
> > make[3]: *** [sub-3rdparty-freetype-make_first] Error 3
> >
> > [1] http://autobuild.buildroot.net/results/219162ba616289f799a5053c4dcc6b8574284283
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> So since Qt 5.8, both freetype and harfbuzz are mandatory for the GUI
> support ?
Do not know if 'mandatory', but at the moment qt-provided/built-in
freetype/harfbuzz are used by both versions (5.6/5.8) in case
GUI is enabled...
I can try without freetype/harfbuzz but I think this will lead to
no/very poor font support (maybe bitmap fonts?)...
>
> Should we make these additional dependencies only exist for the Qt
> latest version (they were not needed for Qt 5.6) ?
If using the system/buildroot provided libraries is preferred it should
be done for both versions...
Regards,
Peter
>
> Thanks!
>
> Thomas
next prev parent reply other threads:[~2017-02-10 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 22:30 [Buildroot] [PATCH v1 1/2] qt5base: use system/buildroot provided freetype Peter Seiderer
2017-02-09 22:30 ` [Buildroot] [PATCH v1 2/2] WIP: qt5base: use system/buildroot provided harfbuzz Peter Seiderer
2017-02-10 16:12 ` Peter Seiderer
2017-02-11 18:20 ` Thomas Petazzoni
2017-02-11 21:35 ` Peter Seiderer
2017-02-10 8:36 ` [Buildroot] [PATCH v1 1/2] qt5base: use system/buildroot provided freetype Thomas Petazzoni
2017-02-10 14:36 ` Peter Seiderer [this message]
2017-02-10 14:59 ` 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=20170210153619.2d894fa5@gmx.net \
--to=ps.report@gmx.net \
--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 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.