From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] XSERVER [was Re: svn commit: trunk/buildroot/package: cairo dillo libgtk12 libgtk2 metacity p etc...]
Date: Mon, 5 Feb 2007 11:57:55 +0100 [thread overview]
Message-ID: <20070205105755.GG5399@aon.at> (raw)
In-Reply-To: <8803519.post@talk.nabble.com>
On Mon, Feb 05, 2007 at 01:59:38AM -0800, Daniel Laird wrote:
>
>
>aldot wrote:
>>
>> Author: aldot
>> Date: 2007-02-04 11:47:41 -0800 (Sun, 04 Feb 2007)
>> New Revision: 17769
>>
>> Log:
>> - the $(XSERVER) target can be provided by different X server impls.
>> Adjust users
>> - rdesktop needs an xserver impl
>>
>>
>> Modified:
>> trunk/buildroot/package/Makefile.in
>> trunk/buildroot/package/cairo/cairo.mk
>> trunk/buildroot/package/dillo/dillo.mk
>> trunk/buildroot/package/libgtk12/libgtk12.mk
>> trunk/buildroot/package/libgtk2/libgtk2.mk
>> trunk/buildroot/package/metacity/metacity.mk
>> trunk/buildroot/package/pango/pango.mk
>> trunk/buildroot/package/rdesktop/rdesktop.mk
>> trunk/buildroot/package/rxvt/rxvt.mk
>> trunk/buildroot/package/xorg/xorg.mk
>>
>> ...
>>
>Cool, I posted a thread the other day about how to deal with packages that
I must have missed that thread, sorry.
>could be configured with X and without X(in the case where you use DirectFB
>for example)
>I presume we could add a DirectFB option to the list of XSERVERS: (as there
>is a DirectFB Xserver)
>
>Secondly, Would you also have anything against if XSERVERS empty then
>configure packages as --without-x (or equivalent)
>
>Then we could also check if DirectFB then use --enable-directfb for packages
>that care.
>
>What do you think.
(1) update directfb t othe current, stable (thus hopefully supported)
version.
DirectFB used to change their API far too fast last time i looked at
it, so it was extremely inconvenient to use. Perhaps this has changed
since then -- it was a couple of years back, two, or maybe three,
dunno.
(2) flesh-out the directfb config to allow for (relatively) fine-grained
configuration: Just bare core / some nifty other stuff that may be
useful.
(3) update XSERVER accordingly
(4) provide an $(ENABLE_DIRECTFB) or the like for use by interrested packages
etc, etc.
The order is significant here, at least from my POV. _First_ fix the
directfb package not to use ancient, deprecated stuff.. YMMV
prev parent reply other threads:[~2007-02-05 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 19:47 [Buildroot] svn commit: trunk/buildroot/package: cairo dillo libgtk12 libgtk2 metacity p etc aldot at uclibc.org
2007-02-05 9:59 ` Daniel Laird
2007-02-05 10:57 ` Bernhard Fischer [this message]
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=20070205105755.GG5399@aon.at \
--to=rep.dot.nop@gmail.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.