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:	<200010032006.e93K6ih16791@laxmls02.socal.rr.com>
X-Sender:	cloder AT pop-server DOT socal DOT rr DOT com (Unverified)
X-Mailer:	QUALCOMM Windows Eudora Pro Version 4.0
Date:	Tue, 03 Oct 2000 13:09:23 -0700
To:	cygwin AT sourceware DOT cygnus DOT com
From:	Chad Loder <cloder AT acm DOT org>
Subject:	Using Visual C++ under Cygwin build system
Mime-Version:	1.0

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.

Has anyone dealt with this problem before? Any suggestions
(or examples)?

Thanks,
	Chad


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

- Raw text -