From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] GTK+ for framebuffer?
Date: Thu, 5 Sep 2013 09:10:54 +0200 [thread overview]
Message-ID: <20130905091054.51fd4ce0@skate> (raw)
In-Reply-To: <20130905060235.GA15735@zuhnb712.ap.bm.net>
Dear Woody Wu,
On Thu, 5 Sep 2013 14:02:35 +0800, Woody Wu wrote:
> Many thanks for your information. Now I feel more clear that I should
> go Gtk/X.org. On the other side, I have no experience on running x.org
> on an embeded system. What things in buildroot I should enable to build
> a minimal system that can at lest run the gtk demons on TinyX? My
> display is just framebuffer. I understand, the question may sounds a
> little stupid. Looking forward for your help.
I believe to get things started enable BR2_PACKAGE_XORG7, enable
BR2_PACKAGE_XSERVER_XORG_SERVER, keep the KDrive/Tiny-X server type,
and enable BR2_PACKAGE_XSERVER_XORG_SERVER_KDRIVE_EVDEV.
Then, you will have Xfbdev on your target, which is the X server. It
has a bunch of options that allows you to specify which evdev device to
use as a mouse and as a keyboard, if you have such input devices on
your system.
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:[~2013-09-05 7:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 10:09 [Buildroot] GTK+ for framebuffer? Woody Wu
2013-09-03 11:31 ` Thomas Petazzoni
2013-09-04 2:40 ` Woody Wu
2013-09-04 7:35 ` Thomas Petazzoni
2013-09-05 6:02 ` Woody Wu
2013-09-05 7:10 ` Thomas Petazzoni [this message]
2013-09-05 8:19 ` Woody Wu
2013-09-09 1:39 ` Woody Wu
2013-09-09 7:08 ` Thomas Petazzoni
2013-09-09 13:16 ` Woody Wu
2013-09-09 13:35 ` 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=20130905091054.51fd4ce0@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 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.