From: Assen Stoyanov <softa@ttechgroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] Matchbox Support
Date: Tue, 15 May 2007 11:46:57 +0300 [thread overview]
Message-ID: <005301c796cd$98e56120$6614a8c0@lap> (raw)
In-Reply-To: 008001c79625$3558b1f0$2600a8c0@engineering5
Hello All,
I am 99% ready with the port of matchbox project. Incl.:
- Matchbox Window Manager
- Matchbox Startup Notification
- Matchbox Desktop
- Matchbox Virtual Keyboard
Also other thinks that are 100% done are:
1) lilo 22.8 (x86 boot loader)
2) tslib 1.0 (touchscreen lib and utils)
3) X11R7 libs (libX11.so)
3.1) libICE.so - Inter Client Exchange library
3.2) libXdmcp.so - X Display Manager Control Protocol library
3.3) libXfixes.so - X Fixes extension library
3.4) libXfont.so - X font libary (used by the X server)
3.5) libXext.so - X Extension library
3.6) libXtst.so - X Test Extensions library
3.7) libXdamage.so - X Damage library
3.8) libXcomposite.so - X Composite library
3.9) libXres.so - X Resources library
3.10) libXrender.so - X Render extension library
3.11) libXrandr.so - X Resize and Rotate extension library
3.12) libXcursor.so - Client-side cursor loading library
3.13) libXft.so - X FreeType library. Client-side fonts with FreeType
3.14) libSM.so - X Session Management library.
3.15) libxkbfile.so - X KBFile utils library.
3.16) libXt.so - X Toolkit library.
3.17) libXmu.so - X Xmu/Xmuu library.
3.18) libXpm.so - X Pixmap library.
3.19) libXaw.so - X Athena Extensions.
4) X11R7 Kdrive (TinyX) Servers (incl. tslib support)
TODOs (this week):
- refactor cairo;
- refactor glib/gtk;
- add jikes java compiler in toolchain;
- add JamVM (java virtual machine)
- add GNU Classpath 0.95 with (optional) GTK/Cairo peers for full awt/swing
support.
My question is - what is the best way to submit all these changes to the
buildroot repository?
Best Regards,
Assen Stoyanov
----- Original Message -----
From: "Christopher Reder" <creder@digitalcpt.com>
To: <buildroot@uclibc.org>
Sent: Monday, May 14, 2007 15:41
Subject: [Buildroot] Matchbox Support
> Hello all. I am using buildroot for a project with an ARM at91rm9200 and
> it
> is working nicely after getting some assistance building. It is building
> a
> file system with busybox and tiny-x and I'd like to incorporate a desktop
> like matchbox in with it. I read that there were a few people
> incorporating
> it into the build but I could not find it in there. Can someone let me
> know
> if it is in there or if they have a patch to add it in?
>
>
>
> Thanks in advance!
> Christopher Reder
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.467 / Virus Database: 269.7.0/804 - Release Date: 5/14/2007
> 4:46 PM
>
>
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.467 / Virus Database: 269.7.0/804 - Release Date: 5/14/2007 4:46 PM
next prev parent reply other threads:[~2007-05-15 8:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 14:21 [Buildroot] kernel patch not applied David Claffey
2007-05-10 15:34 ` David Claffey
2007-05-11 14:31 ` Hans-Christian Egtvedt
2007-05-11 15:40 ` Bernhard Fischer
2007-05-11 16:29 ` David Claffey
2007-05-12 10:31 ` Bernhard Fischer
2007-05-29 20:52 ` David Claffey
2007-05-14 5:21 ` Hans-Christian Egtvedt
2007-05-14 7:11 ` Bernhard Fischer
2007-05-14 12:41 ` [Buildroot] Matchbox Support Christopher Reder
2007-05-15 8:46 ` Assen Stoyanov [this message]
2007-05-15 10:55 ` Peter Korsgaard
2007-05-14 15:25 ` [Buildroot] kernel patch not applied Hans-Christian Egtvedt
2007-05-14 15:34 ` Bernhard Fischer
2007-05-15 7:47 ` Hans-Christian Egtvedt
2007-05-15 8:53 ` Bernhard Fischer
2007-05-15 10:35 ` [Buildroot] Whats happened to Eric? Ulf Samuelsson
2007-05-15 19:04 ` Erik Andersen
2008-11-04 18:19 ` [Buildroot] kernel patch not applied Julien Boibessot
2008-11-04 19:54 ` Bernhard Reutner-Fischer
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='005301c796cd$98e56120$6614a8c0@lap' \
--to=softa@ttechgroup.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