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:	<39DB47A4.18B028F1@comco.com>
Date:	Wed, 04 Oct 2000 10:07:16 -0500
From:	Tadeusz Liszka <tad AT comco DOT com>
Organization:	Altair Engineering, Inc.
X-Mailer:	Mozilla 4.07 [en] (X11; U; IRIX 5.3 IP22)
MIME-Version:	1.0
To:	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	[Fwd: Using Visual C++ under Cygwin build system]

--------------5F71403B9286760362D37D4D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

-- 
Tadeusz
:: The public opinion should be alarmed by its own nonexistence
:: (512)467-0618 ext. 526 ::       Stanislaw J. Lec, trans. TJL
--------------5F71403B9286760362D37D4D
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <39DB4760 DOT 3A9706AF AT comco DOT com>
Date: Wed, 04 Oct 2000 10:06:08 -0500
From: Tadeusz Liszka <tad AT comco DOT com>
Organization: Altair Engineering, Inc.
X-Mailer: Mozilla 4.07 [en] (X11; U; IRIX 5.3 IP22)
MIME-Version: 1.0
To: Matthew Smith <matts AT bluesguitar DOT org>
Subject: Re: Using Visual C++ under Cygwin build system
References: <200010032006 DOT e93K6ih16791 AT laxmls02 DOT socal DOT rr DOT com> <001301c02d84$1dfd0cb0$3c5350d8 AT guinness>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Matthew Smith wrote:
> 
> > 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.

It works for me since 20b (winter 98) without cygpath - all paths for the compiler are
produced as relative to the current dir

There was a problem with Digital FORTRAN - which accepts in pathnames only backslash, and
uses slash for the options (/c not -c), and to add to the confucion its' exec name is
obviously df.exe !!!

There was another problem I had: we had preprocessing utility, built as a part of make, to
produce C files to be compiled .... This preprocessor used extensively exec's to 'mv',
'rm', cat', etc. So the sequence was: DOS->bash->make->bash->pre->exec->rm and pre should
not be compiled with VC - switching back and forth between Windoze and Cygwin calling each
other caused strange hung-ups.

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

-- 
Tadeusz
:: The public opinion should be alarmed by its own nonexistence
:: (512)467-0618 ext. 526 ::       Stanislaw J. Lec, trans. TJL


--------------5F71403B9286760362D37D4D
Content-Type: text/plain; charset=us-ascii

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

- Raw text -