Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From: "Hannu E K Nevalainen" <garbage_collector AT telia DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Problems with Make, VPATH and MS-DOS paths
Date: Mon, 17 Nov 2003 20:31:23 +0100
Message-ID: <NGBBLLIAMFLGJEOAJCCEGEFIDGAA.garbage_collector@telia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <YX54YT93FCIHNL97JG1NJPONWQYSDA.3fb8fcd5@marlin4>
Importance: Normal

> From: Nate Bohlmann
> Sent: Monday, November 17, 2003 5:53 PM

> Hi,
>   I'm having a problem getting MS-DOS paths to work properly with
> VPATH under
> GNU Make 3.80.  The problem is that the VPATH processing tacks on
> a Unix path
> separator ('/') to the end of the VPATH giving me a source file
> name something
> similar to code\src\fw/foo.c.  This is a significant problem for
> the compiler
> I'm using (NOT gcc) since it spits out map and list files based
> on the stem of
> the input source name which it decides is 'fw/foo.c'.
<SNIP>

$ cygpath --help

IMO it should help to solve all your problems. cygpath is part of the base
package so there is no need go looking for it either; if you have cygwin
then you have cygpath too.

/Hannu E K Nevalainen, B.Sc. EE - 59+16.37'N, 17+12.60'E
-- printf("LocalTime: UTC+%02d\n",(DST)? 2:1); --
--END OF MESSAGE--


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