From: Maarten ter Huurne <maarten@treewalker.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] freetype: Add config option for bzip2 compressed font support
Date: Sun, 19 Oct 2014 02:49:36 +0200 [thread overview]
Message-ID: <3620793.9UjUVpDraY@hyperion> (raw)
In-Reply-To: <5442672B.1000500@mind.be>
On Saturday 18 October 2014 15:12:11 Arnout Vandecappelle wrote:
> On 18/10/14 04:39, Maarten ter Huurne wrote:
> > If bzip2 is available, it might still be preferable to not include
> > support for bzip2 compressed fonts, for example to reduce the number
> > of libraries loaded when running a GUI application.
>
> I don't agree with this. The impact will be really small, both for memory
> size and for load time - especially because any application using
> freetype will most likely load much larger GUI libraries. If you're
> working at such details, you'll unavoidably have to do some manual hacks
> to get it even better. So I don't think it makes sense to add a config
> option for it - we try to keep the number of config options in check.
>
> So unless you can show me a use case where it makes a real impact, it's a
> NACK.
The menu we're using (GMenu2X) uses FreeType via SDL_ttf, not via a large
GUI toolkit. Dropping the libbzip2 dependency reduces the number of
libraries loaded from 12 to 11. I haven't benchmarked how many milliseconds
of a difference that makes in startup time.
Note that the only place where bzip2 compression is actually supported by
FreeType is when opening PCF files. Disabling the feature has no effect on
support for other font formats such as TTF.
Bye,
Maarten
next prev parent reply other threads:[~2014-10-19 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 2:39 [Buildroot] [PATCH] freetype: Add config option for bzip2 compressed font support Maarten ter Huurne
2014-10-18 12:48 ` Maxime Hadjinlian
2014-10-18 13:12 ` Arnout Vandecappelle
2014-10-19 0:49 ` Maarten ter Huurne [this message]
2014-10-19 20:39 ` Arnout Vandecappelle
2015-02-03 15:59 ` Peter Korsgaard
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=3620793.9UjUVpDraY@hyperion \
--to=maarten@treewalker.org \
--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