Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Mon, 20 May 2002 10:00:37 +0200 (MEST) From: "S. L." To: cygwin AT cygwin DOT com MIME-Version: 1.0 References: <20020520064117 DOT GA18463 AT redhat DOT com> Subject: Re: GTK on cygwin X-Priority: 3 (Normal) X-Authenticated-Sender: #0006551723 AT gmx DOT net X-Authenticated-IP: [194.102.244.61] Message-ID: <1830.1021881637@www43.gmx.net> X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit [...] > >> > CYGWIN is really a great thing. I want to use GTK natively on > Windows, [...] > Just to add to the thread, I assume that if GTK+ can be built using mingw, > it should be pretty easy to build it for native cygwin. Have you tried > just building it with Cygwin's gcc? > > cgf [...] ... Just to answer to the just-added-to-the-thread :) Yes, I have. And I am still trying. On the serious hand, now, there are several issues regarding GTK+/cygwin: 1. unlike tcl/tk, there was never a gtk+ port on cygwin 2. like the tcl/tk there are versions more closely to be "portable" than others 3. like the tcl/tk case, both gtk+ and cygwin are evolving independently, so any building assumptions in a particular moment are not sync'd. 4. the most despairing thing is the version 2.0 of gtk+: while 1.2.x series were not ported on cygwin, and they required just glib and gtk+ tarballs, the 2.0.x series come with 4 tarballs, and have iconv and pkg-config as dependencies. Ugly! 5. the man who is the most involved in gtk+ porting to win32, tml, >/dev/null 's any cygwin related question. And he's right. SLao -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/