From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] gtk+
Date: Tue, 3 Jul 2012 11:11:06 +0200 [thread overview]
Message-ID: <20120703111106.7f544276@skate> (raw)
In-Reply-To: <1341046722.72419.YahooMailNeo@web160706.mail.bf1.yahoo.com>
Hello Zoran,
Could you please post future questions about Buildroot directly on the
mailing list? I'm Cc'ing the list now.
Le Sat, 30 Jun 2012 01:58:42 -0700 (PDT),
Zoran Djordjevic <djdjdjole@yahoo.com> a ?crit :
> I recently read? some answer you put regarding gtkmm question. What make me
> interested in that answer was your declaration: "We already have gtk+ support
> in Buildroot...".
> My question is what should I check in menuconfig to enable gtk+ support ?
gtk+ requires:
* A graphic backend, either DirectFB or X.org. The DirectFB backend is
not very well maintained, so I'd say you'll probably have more luck
with the X.org backend. So you have to enable a X.org server in
your Buildroot configuration.
* 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
Or by looking at the help text for BR2_PACKAGE_LIBGTK2 in menuconfig.
Hope this helps,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next parent reply other threads:[~2012-07-03 9:11 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 ` Thomas Petazzoni [this message]
2012-07-03 15:28 ` [Buildroot] gtk+ Sven Neumann
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=20120703111106.7f544276@skate \
--to=thomas.petazzoni@free-electrons.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