Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <001301c02d84$1dfd0cb0$3c5350d8@guinness>
From: "Matthew Smith" <matts AT bluesguitar DOT org>
To: <cygwin AT sourceware DOT cygnus DOT com>, "Chad Loder" <cloder AT acm DOT org>
References: <200010032006 DOT e93K6ih16791 AT laxmls02 DOT socal DOT rr DOT com>
Subject: Re: Using Visual C++ under Cygwin build system
Date: Tue, 3 Oct 2000 16:51:42 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

> Hello. I am developing a build system using Cygwin (GNU make, bash,
> etc.) on Windows 2000.
>
> Some of our subsystems must be built using Visual C++. Obviously
> Visual C++ will not understand paths like "/c/foo/bar.c" (where
> /c is the Cygwin mounted C: drive). However, since GNU make will
> be producing targets and processing prerequisites with precisely
> those kinds of paths, I foresee problems.

Use the 'cygpath' program included with cygwin.  It will convert back and
forth between cygwin and windows paths.  An example of using this in a make
file would be like this:

RES_FILE := $(shell cygpath -w $(OBJ_DIR)/resource.o)

cheers,
-Matt Smith



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com