X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Mark Hadfield <m DOT hadfield AT niwa DOT co DOT nz>
Subject:  Re: 3.81 and windows paths
Date:  Fri, 28 Jul 2006 13:06:10 +1200
Lines: 38
Message-ID: <eabnu3$i6v$1@sea.gmane.org>
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=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
In-Reply-To: <008e01c6b1cc$76021310$280aa8c0@oius.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

William Sheehan wrote:
>Christopher Faylor wrote:
>> There is no advantage using cygwin if you want to use a Makefile
 >> which contains MS-DOS paths.  Using MinGW
 >> makes perfect sense in that case.
> 
> I strongly disagree with this statement.  A primary benefit of using Cygwin
> is that so many Linux-like tools are available from one central installer.
> If you have a Makefile system that uses Cygwin for more than just the make
> binary and binutils (aka more than what MinGW provides), it becomes
> irritating to developers that they need to install at least two software
> products (Cygwin and MinGW in this case) and create special path voodoo just
> for one product.

I disagree with both of you.

I use Cygwin tools, including Gnu make, to build an ocean model. This 
system supports both Cygwin (g95-cygwin) and non-Cygwin (Compaq, 
g95-mingw) Fortran compilers. (These days I use g95-cygwin mostly, but 
there are good reasons to support the others.)

I don't use Mingw make because the build system was developed on Unix 
and I just don't want the grief of porting it to a naked Windows system. 
BUT I wasn't bitten by the removal of Windows mode in make, because I 
always run make in Unix mode. Make doesn't generally see the Windows 
paths. When I need to pass Windows path to the non-Cygwin compilers, I 
create them on the fly with cygpath. This does require a little care 
with quoting, but I've managed to sort out all the problems I've 
encountered.

I won't go into more detail, but I have posted examples of this in the 
past on this list.


-- 
Mark Hadfield          "Kei puwaha te tai nei, Hoea tahi tatou"
m DOT hadfield AT niwa DOT co DOT nz
National Institute for Water and Atmospheric Research (NIWA)


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