From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libgtk2
Date: Tue, 26 Aug 2008 15:48:56 +0200 [thread overview]
Message-ID: <20080826134856.GK2213@mx.loc> (raw)
In-Reply-To: <87k5e3gbne.fsf@macbook.be.48ers.dk>
On Tue, Aug 26, 2008 at 03:15:49PM +0200, Peter Korsgaard wrote:
>>>>>> "laird" == laird <laird@uclibc.org> writes:
>
> laird> Author: laird
> laird> Date: 2008-08-26 05:19:29 -0700 (Tue, 26 Aug 2008)
> laird> New Revision: 23204
>
>Welcome!
>
> laird> Log:
> laird> The changes below add better support for DirectFB and libgtk2.
> laird> Should be no different for X builds.
>
>Could you please check these things in seperately?
>
> laird> Changeset:
> laird> Modified: trunk/buildroot/package/libgtk2/Config.in
> laird> ===================================================================
> laird> --- trunk/buildroot/package/libgtk2/Config.in 2008-08-26 01:32:33 UTC (rev 23203)
> laird> +++ trunk/buildroot/package/libgtk2/Config.in 2008-08-26 12:19:29 UTC (rev 23204)
> laird> @@ -2,14 +2,13 @@
> laird> bool "libgtk2"
> laird> select BR2_PACKAGE_ATK
> laird> select BR2_PACKAGE_CAIRO
> laird> - select BR2_PACKAGE_CUPS
>
>Shouldn't that instead be something like:
>
>select BR2_PACKAGE_CUPS if BR2_PACKAGE_XORG||BR2_PACKAGE_XORG7||BR2_PACKAGE_TINYX
This was recently changed (for the bad, imho).
Previously, we had a "choice" for either of
XSERVER_none
XSERVER_xorg7
XSERVER_tinyx
XSERVER_xggi
With this scheme, you could quickly distinguish if and if yes then which
xserver was selected:
depends on !BR2_XSERVER_none
to depend on any xserver etc.
Peter, was it you who changed this xserver choice? What was
the rationale?
next prev parent reply other threads:[~2008-08-26 13:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 12:19 [Buildroot] svn commit: trunk/buildroot/package/libgtk2 laird at uclibc.org
2008-08-26 13:15 ` Peter Korsgaard
2008-08-26 13:32 ` Daniel Laird
2008-08-26 13:38 ` Peter Korsgaard
2008-08-26 14:04 ` Bernhard Reutner-Fischer
2008-08-26 14:07 ` Bernhard Reutner-Fischer
2008-08-26 14:54 ` Peter Korsgaard
2008-08-26 13:48 ` Bernhard Reutner-Fischer [this message]
2008-08-26 14:07 ` Peter Korsgaard
2008-08-26 14:11 ` Bernhard Reutner-Fischer
2008-08-26 14:13 ` Daniel Laird
2008-08-26 13:42 ` Ormund Williams
2008-08-26 13:49 ` Daniel Laird
-- strict thread matches above, loose matches on Subject: below --
2009-01-18 10:57 ulf at uclibc.org
2009-01-18 11:05 ` Peter Korsgaard
2009-01-18 13:11 ` Sven Neumann
2009-01-18 13:43 ` Daniel Laird
2009-01-18 13:48 ` Peter Korsgaard
2009-01-14 22:11 ulf at uclibc.org
2009-01-15 8:36 ` Thomas Lundquist
2009-01-15 20:18 ` Ulf Samuelsson
2009-01-15 20:26 ` Peter Korsgaard
2009-01-15 20:37 ` Ulf Samuelsson
2008-12-31 9:35 jacmet at uclibc.org
2008-12-26 15:36 jacmet at uclibc.org
2008-12-26 15:36 jacmet at uclibc.org
2008-10-27 9:45 jacmet at uclibc.org
2008-10-18 7:00 jacmet at uclibc.org
2008-08-26 13:45 laird at uclibc.org
2008-07-08 10:09 ulf at uclibc.org
2008-07-07 11:09 ulf at uclibc.org
2008-07-06 6:25 ulf at uclibc.org
2007-02-01 19:20 andersen at uclibc.org
2007-01-17 11:27 jacmet at uclibc.org
2007-01-17 0:04 andersen at uclibc.org
2007-01-14 23:27 andersen at uclibc.org
2007-01-14 23:26 andersen at uclibc.org
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=20080826134856.GK2213@mx.loc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox