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
Date: Mon, 17 Nov 2003 12:52:59 -0700
From: Nate Bohlmann <nbohlmann AT cso DOT atmel DOT com>
Subject: Re: RE: Problems with Make, VPATH and MS-DOS paths
In-reply-to: <NGBBLLIAMFLGJEOAJCCEGEFIDGAA.garbage_collector@telia.com>
To: cygwin AT cygwin DOT com
Message-id: <YW4165DBJI2UA8DBATSBWUNHZU85V.3fb9271b@marlin4>
Organization: Atmel Corporation
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3 (Normal)

11/17/03 12:31:23 PM, Hannu E K Nevalainen <garbage_collector AT telia DOT com> wrote:

>> 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.
<SNIP>

How exactly does a command line tool help with VPATH'ing inside of Make?







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