Date: Thu, 27 Jul 2006 19:35:55 -0400
From: Bob Rossi <bob_rossi AT cox DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: 3.81 and windows paths
Message-ID: <20060727233555.GE27890@brasko.net>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20060727221136 DOT GD6653 AT trixie DOT casa DOT cgf DOT cx> <008e01c6b1cc$76021310$280aa8c0 AT oius DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <008e01c6b1cc$76021310$280aa8c0@oius.com>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

> I can imagine that the immediate response to this complaint will be "fix
> your Makefiles to work with Cygwin if it's such an important component."  As
> others have mentioned, this is no simple task in very large Makefile systems
> that support a wide variety of compilation toolchains.  Cygwin make has
> supported Win32 paths for a long time, so much that I would say that people
> have come to rely on it.  I am not saying that the changes are impossible;
> just that it is a larger inconvenience than some may realize.

I second this thought. I'm stuck on 3.80 until I have the time to figure
out how to port to 3.81. I may simply wait for 3.82 and hope the feature
removed comes back.

Bob Rossi

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