Message-ID: <4A3FD71B.4080405@sidefx.com>
Date: Mon, 22 Jun 2009 15:10:19 -0400
From: Edward Lam <edward@sidefx.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: weird feature
References: <890c978b4ab3063f3d602834a99501f1@mail.smartmobili.com> <5bbe440b12fc56489f671909ca240bc3@mail.smartmobili.com> <a9a7d86093c421e3c645c2504ea9b6fe@mail.smartmobili.com> <4A3FAC26.7030402@cygwin.com> <4A3FD3BE.20601@gmail.com>
In-Reply-To: <4A3FD3BE.20601@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Dave Korn wrote:
> Larry Hall (Cygwin) wrote:
> 
>>   2. Use 'cygpath' to convert from DOS to Cygwin path forms and back as
>>      needed.  This can get tricky/cumbersome in some cases.
> 
>   It can be a lot easier if you have a Makefile-based build system, where you
> can do the conversion on things that you know need converting like $(SRC) and
> $(OBJS) and $(INCLUDEPATH) but not things like $(CFLAGS), rather than if you
> try and write shell scripts to wrap the compiler and parse the options.  That
> can also be a good approach, but more work to get it completely right.

In my experience, adding cygcheck does slow down a large build system 
*significantly* when adding cygpath's though.

-Edward

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple