Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <4301AB44.7DDCB59B@dessent.net>
Date: Tue, 16 Aug 2005 02:00:52 -0700
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin mailing list <cygwin AT cygwin DOT com>
Subject: Re: May g++ output windows-style paths instead of cygwin-style one?
References: <000301c5a23d$04f46f00$cf34000a AT sven>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Angel Tsankov wrote:

> Is there any way I can force the cygwin build of g++ to output folders
> using windows style (e.g. c:\folder\file) instead of cygwin style
> (/cygdrive/c/folder/file) when writing dependency files (-MM option)?

No, there's no way to do that.  You could probably come up with a perl
command that would filter the files through cygpath to convert the
paths, though.

> I have this problem, 'cause I use a windows build of make 3.81beta3
> and it does not recognize cygwin style paths.
> The latest cygwin build of make is 3.80, which has some bugs, and I
> cannot use it.

I think it would be more productive for you to get Cygwin make working
than to try to jerry-rig a windows make into a posix environment.  If
you are running into a specific bug in the current packaged version that
is fixed upstream, then you should document it here and the Cygwin
package maintainer might release an updated package.

Brian

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