Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] freetype: Add config option for bzip2 compressed font support
Date: Tue, 03 Feb 2015 16:59:26 +0100	[thread overview]
Message-ID: <87pp9rasv5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <5444216A.3060103@mind.be> (Arnout Vandecappelle's message of "Sun, 19 Oct 2014 22:39:06 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

Hi,

>>> 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.

 >  Okay, let's leave it up to the Benevolent Dictator to make the call. If it's a
 > go, and the depends on is changed into a select like Maxime requested, it gets
 > my Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

Sorry - We discussed it at the Buildroot developer days, and agreed that
it it isn't worth the trouble to have an explicit option for this.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2015-02-03 15:59 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
2014-10-19 20:39     ` Arnout Vandecappelle
2015-02-03 15:59       ` Peter Korsgaard [this message]

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=87pp9rasv5.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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