Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: package package/cairo package/dillo pac etc...
Date: Sat, 11 Aug 2007 14:00:42 +0300	[thread overview]
Message-ID: <46BD96DA.1000004@promwad.com> (raw)
In-Reply-To: <20070810190804.39EE4A65AA@busybox.net>

andersen at uclibc.org ?????:
> Author: andersen
> Date: 2007-08-10 12:07:51 -0700 (Fri, 10 Aug 2007)
> New Revision: 19424
> 
> Log:
> Merge in X11R7 patches from Julien Letessier, posted 04 Jul 2007.  Doesn't
> quite work yet for me, but this clearly is a huge project and not having it
> quite work on the first pass is hardly unexpected.  We definately want this
> stuff in buildroot.
> 
> 
> Added:
>    trunk/buildroot/package/cairo/Config.in
>    trunk/buildroot/package/dillo/Config.in
>    trunk/buildroot/package/gettext/gettext.mk
>    trunk/buildroot/package/libgtk12/Config.in
>    trunk/buildroot/package/libgtk2/Config.in
>    trunk/buildroot/package/metacity/Config.in
>    trunk/buildroot/package/rdesktop/Config.in
>    trunk/buildroot/package/tinyx/Config.in
>    trunk/buildroot/package/xorg/Config.in
>    trunk/buildroot/package/xorg/xorg.mk
> 

Hello, in X11R7 merge you have dropped tinyx dependency for gtk12,gtk2,cairo.
The patch below allows gtk to be build against tinyx:

------

Index: package/libgtk12/Config.in
===================================================================
--- package/libgtk12/Config.in  (revision 19425)
+++ package/libgtk12/Config.in  (working copy)
@@ -2,7 +2,7 @@
         bool "libgtk12"
         default n
         select BR2_PACKAGE_LIBGLIB12
-       depends on BR2_PACKAGE_XORG||BR2_PACKAGE_XORG7
+       depends on BR2_PACKAGE_XORG||BR2_PACKAGE_XORG7||BR2_PACKAGE_TINYX
         help
           The GTK+ graphical user interface library

Index: package/libgtk2/Config.in
===================================================================
--- package/libgtk2/Config.in   (revision 19425)
+++ package/libgtk2/Config.in   (working copy)
@@ -7,7 +7,7 @@
         select BR2_PACKAGE_JPEG
         select BR2_PACKAGE_TIFF
         select BR2_PACKAGE_LIBPNG
-       depends on BR2_PACKAGE_XORG||BR2_PACKAGE_XORG7
+       depends on BR2_PACKAGE_XORG||BR2_PACKAGE_XORG7||BR2_PACKAGE_TINYX
         help
           The GTK+ version 2 graphical user interface library

Index: package/cairo/Config.in
===================================================================
--- package/cairo/Config.in     (revision 19425)
+++ package/cairo/Config.in     (working copy)
@@ -3,7 +3,7 @@
         default n
         select BR2_PACKAGE_PKGCONFIG
         select BR2_PACKAGE_LIBPNG
-       depends on BR2_PACKAGE_XORG||BR2_PACKAGE_XORG7
+       depends on BR2_PACKAGE_XORG||BR2_PACKAGE_XORG7||BR2_PACKAGE_TINYX
         help
           Cairo is a 2D graphics library with support for multiple
           output devices. Currently supported output targets include

      reply	other threads:[~2007-08-11 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 19:08 [Buildroot] svn commit: trunk/buildroot: package package/cairo package/dillo pac etc andersen at uclibc.org
2007-08-11 11:00 ` Ivan Kuten [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=46BD96DA.1000004@promwad.com \
    --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