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: Tue, 11 Jun 2002 11:59:32 +0200 (MEST) From: "S. L." To: Nicholas Wourms Cc: khan AT nanotech DOT wisc DOT edu, michael AT internetdiscovery DOT com, cygwin AT cygwin DOT com MIME-Version: 1.0 References: <20020610123717 DOT 44820 DOT qmail AT web21007 DOT mail DOT yahoo DOT com> Subject: Re: Updated Tcl Tk and Tix X-Priority: 3 (Normal) X-Authenticated-Sender: #0006551723 AT gmx DOT net X-Authenticated-IP: [194.102.244.61] Message-ID: <30725.1023789572@www31.gmx.net> X-Flags: 0001 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit [...] > Now you've confused me, I'm not sure what you are getting at here... Why > is what I'm saying off topic? The tcl/tk suite that uses mingw/w32api is > already distributed in the mainline distribution. The point I was making [...] You're right about tcl/tk "mingw/w32api", but I'd consider that package (20001125) as an example of "how must not be provided" cygwin packages. [...] > is the same one you summerized in the end, we need an autotools enabled > tcltk suite which generates both a Win32api and POSIX versions. To > further elaborate, maybe the Win32 libraries ought to reside in the > win32api directory with it's own version of {Tk Tcl}Config.sh residing > there, too. Perhaps wrapper scripts could be used, in the same manner as [...] Here the confusion I was talking, rises again. All GUI shells from tcl/tk suite, would use win32api, wether they are cygwin (POSIX enabled), or mingw. 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/