From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] gtk+
Date: Tue, 03 Jul 2012 17:28:37 +0200 [thread overview]
Message-ID: <1341329317.31903.16.camel@sven> (raw)
In-Reply-To: <20120703111106.7f544276@skate>
On Tue, 2012-07-03 at 11:11 +0200, Thomas Petazzoni wrote:
> gtk+ requires:
> * A toolchain with wide char support and C++ support.
>
> These dependencies can be found by reading package/libgtk2/Config.in:
>
> config BR2_PACKAGE_LIBGTK2
> bool "libgtk2"
> [...]
> depends on BR2_PACKAGE_XORG7||BR2_PACKAGE_DIRECTFB
> depends on BR2_USE_WCHAR # glib2
> depends on BR2_INSTALL_LIBSTDCPP # pango
> help
> The GTK+ version 2 graphical user interface library
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.
Regards,
Sven
next prev parent reply other threads:[~2012-07-03 15:28 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 [this message]
2012-07-03 15:59 ` Thomas Petazzoni
2012-07-03 19:07 ` Peter Korsgaard
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=1341329317.31903.16.camel@sven \
--to=s.neumann@raumfeld.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