Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3CD51E19.5A7708D7@yahoo.com>
Date: Sun, 05 May 2002 07:57:13 -0400
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: Earnie Boyd <Cygwin-Apps AT cygwin DOT com>
X-Accept-Language: en
MIME-Version: 1.0
To: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
CC: Earnie Boyd <Cygwin-Apps AT cygwin DOT com>,
   Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
Subject: Re: new cygwin package: cgoban
References: <FC169E059D1A0442A04C40F86D9BA7600C5FB0 AT itdomain003 DOT itdomain DOT net DOT au> <3CD3DD22 DOT 76BD5C0 AT yahoo DOT com> <3CD428C7 DOT 8000206 AT ece DOT gatech DOT edu> <3CD42CF7 DOT 874A8C49 AT yahoo DOT com> <3CD440EF DOT 9070405 AT ece DOT gatech DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Charles Wilson wrote:

>
> (*) counter argument: gtk+ on cygwin currently uses X.  However, the
> code is THERE to use native MS windowing -- because there is a native MS
> port (on a separate CVS branch).  It might be possible, some time in the
> future, to have TWO different "gtk+" builds on cygwin: and X one and an
> MS one (it is not CURRENTLY possible to do that).  But, in that
> eventuality, you could then have a whole SLEW of cygwin ports of
> gtk+-based programs that could be compile as "X" apps or as "native MS
> windowing" apps -- depending on which version of the gtk+ libs they were
> linked against.  But should we borrow trouble against something that may
> never happen? (Tor Lilqvist, maintainer of the windows port of gtk+,
> doesn't seem too enthusiastic about refactoring to separate his
> native-windowing stuff from his msvcrt-not-glibc-runtime stuff; it's all
> #if _MSWIN ...).

Ah, now the point at which I was trying to drive home at.  Yes, IMO, we should
"borrow trouble" as that trouble is most likely to happen.  It's much like the
MinGW libraries where the headers and libraries need to be segregated, so will
these apps.

Earnie.