Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Wed, 22 Nov 2000 20:34:19 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Texinfo-4.0 Message-ID: <20001122203419.A13916@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20001123003237 DOT 15725 DOT qmail AT web113 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20001123003237.15725.qmail@web113.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, Nov 22, 2000 at 04:32:37PM -0800 On Wed, Nov 22, 2000 at 04:32:37PM -0800, Earnie Boyd wrote: >--- Christopher Faylor wrote: >> > >> >Like what? How? IMO, the confusion and breakage is with the way the specs >> are >> >now. >> >> For people who are using gcc to compile Windows programs for one. > >I don't see this. The -mno-cygwin switch would add the appropriate windows >defines. Assuming that you're compiling with -mno-cygwin. You can write Windows programs without using -mno-cygwin. I assume that many people do this, in fact. >> For >> another, I'm sure that there are packages out there that are actually >> doing the right thing for the wrong reason under 'ifdef WIN32' control. >> > >I've been using it for sometime and have built somewhere around 40 packages >with my changes to the specs file. The unix version of tcl works nicely, of >course, tk requires X. Well, that's an argument against the change, then. The windows version of tcl/tk wouldn't be built. cgf