From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] gtkmm in buildroot toolchain
Date: Fri, 27 Jan 2012 11:19:28 +0100 [thread overview]
Message-ID: <20120127111928.3e881f03@skate> (raw)
In-Reply-To: <loom.20120127T095631-99@post.gmane.org>
Hello,
Le Fri, 27 Jan 2012 08:56:57 +0000 (UTC),
Willy <willy@willygroup.org> a ?crit :
> I've some program written in c++ and gtkmm.
>
> Which is the better way to compile them for my embedded system
> between:
>
> 1. Add (somehow) libgtkmm (and other needed libraries) in buildroot
> toolchain 2. Rewrite entirely my programs with gtk+ (and use always
> it in future) 3. Use another graphic library and rewrite all
All options are possible of course, but option 1) is the one that will
allow you to re-use your software as-is. We already have gtk+ support
in Buildroot, and I don't think that gtkmm has many more dependencies
outside of gtk+, so it should be relatively easy to integrate into
Buildroot.
> PS: I need more documentation for buildroot, exist some good book or
> forum for rookie users?
There is some documentation in the Buildroot sources, run 'make manual'
to generate the documentation.
You can also read the documentation online at
http://buildroot.org/downloads/buildroot.html.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-01-27 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 8:56 [Buildroot] gtkmm in buildroot toolchain Willy
2012-01-27 10:19 ` Thomas Petazzoni [this message]
2012-01-27 12:49 ` Michael S. Zick
2012-01-27 14:11 ` Willy
2012-01-27 14:27 ` Michael S. Zick
2012-01-27 14:38 ` Willy
2012-01-27 15:14 ` Thomas Petazzoni
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=20120127111928.3e881f03@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