From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] building tiny-x or x11R7 with latest snapshot
Date: Mon, 27 Aug 2007 16:24:27 +0300 [thread overview]
Message-ID: <20070827162427.2c3bb806@newbox> (raw)
In-Reply-To: <01cc01c7e757$3e1bf8a0$7201820a@atmel.com>
On Sat, 25 Aug 2007 21:55:10 +0200
Ulf Samuelsson wrote:
> >>
> >> Hi Ulf,
> >>
> >> If we cant build either Tinyx or Xorg or X11 then how else can we build
> >> cairo,pango,gtk and other stuff. i am trying to build a decent toolchain
> >> with all library for arm926ejs but i see that most of these are not
> >> supported for am926ejs
> >>
> >> Is there any possibilities that i can build just cairo pango gtk2 without
> >> the need for x softwares. Once i build all this later can we integrate these
> >> with x softwares.
> >>
>
> > Hello all,
> >
> > I managed to build cairo, pango and gtk2 but with dependency on DirectFB - I need
> > to modify flags to configure and dependencies. TinyX is buildable but seems only
> > gtk-1.2 run on top of it. Xorg-7.2 and X11-R6 are not buildable and require a lot of hands work.
> >
>
> Pls send your modifications so they can be integrated, then.
>
> Best Regards
> Ulf Samuelsson
Hi, unfortunately it was an ugly hack not suitable to be released as patch and I
deleted/rebuilded buildroot many times since then. I try in upcoming week or next week to arrive with something
suitable to be applied.
Best regards,
Ivan
next prev parent reply other threads:[~2007-08-27 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 19:23 [Buildroot] building tiny-x or x11R7 with latest snapshot Christopher Reder
2007-08-20 22:30 ` Ulf Samuelsson
2007-08-24 5:55 ` Hebbar
2007-08-25 12:46 ` Ivan Kuten
2007-08-25 14:46 ` Hebbar
[not found] ` <01cc01c7e757$3e1bf8a0$7201820a@atmel.com>
2007-08-27 13:24 ` Ivan Kuten [this message]
2007-09-10 21:25 ` Ivan Kuten
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=20070827162427.2c3bb806@newbox \
--to=ivan.kuten@promwad.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