All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] gtk+
Date: Tue, 03 Jul 2012 21:07:12 +0200	[thread overview]
Message-ID: <87mx3g1x5r.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120703175921.508fc6fc@skate> (Thomas Petazzoni's message of "Tue, 3 Jul 2012 17:59:21 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 >> I don't quite understand why pango needs C++ support though. As far as I
 >> know it is written in plain C. The pango Config.in file refers to
 >> freetype:
 >> 
 >> depends on BR2_INSTALL_LIBSTDCPP # freetype support
 >> 
 >> But freetype itself doesn't depend on C++ support.

 Thomas> I haven't looked in details, but:

 Thomas> commit 1c4dbb5fa7df89731e5d59f680e9dc34f24f8835
 Thomas> Author: Peter Korsgaard <jacmet@sunsite.dk>
 Thomas> Date:   Mon Aug 30 10:02:39 2010 +0200

 Thomas>     pango: needs C++ for freetype handling

 Thomas>     Pango was recently updated to v1.28 as a dependency of
 Thomas>     webkit, but its freetype support has unfortunately been
 Thomas>     rewritten with parts in C++ (since pango 1.25), so adjust
 Thomas>     dependencies of pango and users of it to require C++
 Thomas>     support.

Ahh yes, the harfbuzz text shaping engine:

find -name \*.cc
./pango/opentype/hb-font.cc
./pango/opentype/hb-ot-layout.cc
./pango/opentype/main.cc

http://www.freedesktop.org/wiki/Software/HarfBuzz

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-07-03 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1341046722.72419.YahooMailNeo@web160706.mail.bf1.yahoo.com>
2012-07-03  9:11 ` [Buildroot] gtk+ Thomas Petazzoni
2012-07-03 15:28   ` Sven Neumann
2012-07-03 15:59     ` Thomas Petazzoni
2012-07-03 19:07       ` Peter Korsgaard [this message]
2012-07-03 21:52         ` Sven Neumann

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=87mx3g1x5r.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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 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.