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
Message-ID: <430A1F2C.2070201@msa.hinet.net>
Date: Tue, 23 Aug 2005 02:53:32 +0800
From: Shaddy Baddah <Shaddy DOT Baddah AT msa DOT hinet DOT net>
Reply-To: Shaddy DOT Baddah AT msa DOT hinet DOT net, cygwin AT cygwin DOT com
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Rationale sought: XEmacs 21.5.16 (test) build disabling MS windows  toolkit
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

I had a play with the XEmacs 21.5.16-1 build (which is the [test]
version atm). I noticed that, unlike the 21.4.17-1 and 21.4.15-1 build,
XEmacs could not be started using the native MS windows toolkit.

A quick look at the source package confirmed that support was explicitly
disabled:
/usr/src/xemacs-21.5.16-1.sh:130:    --with_msw=no
                \

Seeing as this is different from the 21.4 builds, any clues as to the
rationale behind this?

The prominent thing that comes to mind is that, other than tty, it would
seem plausible to choose one windowing toolkit, that being X, and stick
with it to avoid dependencies (for example, you could still build with
GTK support as well if you could handle having the extra dependency).

However, I would have thought that as there is no extra dependency (the
MS windows toolkit is always going to be there), that there would be no
need to disable it.

I hope that if the rationale isn't compelling, that when this build gets
promoted to [curr] that it does bring in the MS windows support, as it
is handy.

TIA,
Shaddy

--
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/