Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Thu, 13 Jan 2005 15:34:40 +0000
From: Roger Leigh <roger DOT leigh AT epictechnology DOT co DOT uk>
To: cygwin AT cygwin DOT com
Subject: Building GTK+ 2.6 on Cygwin
Message-ID: <20050113153440.GA5680@epictechnology.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-GPG-Key: 0x25BFB848
X-Debian: testing/unstable
X-OS-Uptime: 15:28:59 up  1:11,  3 users,  load average: 0.09, 0.08, 0.04
User-Agent: Mutt/1.5.6+20040907i

For anyone wanting to build GTK+ on Cygwin, some patches and comments
are here:

http://bugzilla.gnome.org/show_bug.cgi?id=163913
http://bugzilla.gnome.org/show_bug.cgi?id=163914
http://bugzilla.gnome.org/show_bug.cgi?id=163917

Those fix the most obvious build issues.  I'm currently still getting
odd linker errors for some bits, but I've not yet been able to
reproduce them sensibly (i.e. it worked the first time, but applying
the patches to a clean tree doesn't work)--I think something external
to the tree is to blame.  Once built, gtk-demo segfaults; I haven't
yet found the cause, because gdb doesn't give any sensible backtraces.


Regards,
Roger

-- 
Roger Leigh

                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/