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:	Tue, 29 Oct 2002 06:42:30 -0800 (PST)
From:	"Peter A. Castro" <doctor AT fruitbat DOT org>
To:	Christophe Dupre <duprec AT scorec DOT rpi DOT edu>
cc:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin, GNU make and VC++ ?
In-Reply-To:	<3DBE05B9.6050301@scorec.rpi.edu>
Message-ID:	<Pine.LNX.4.21.0210290639110.20290-100000@gremlin.fruitbat.org>
MIME-Version:	1.0

On Mon, 28 Oct 2002, Christophe Dupre wrote:

> Hello everyone,
> I'm trying to recompile a homegrown program that was originaly
> developped for Unix under Windows. We were successful in compiling this
> program with the cygwin-supplied gcc using our current Makefile.
> 
> Now we'd like to recompile with the 'native' compiler, cl.exe provided
> with Visual Studio, as some believe the native compile would produce
> faster binaries (it's a long-running analysis code - even 5% speedup
> would be significant). Also, the gcc binary can't seem to be able to
> allocate more than 1024MB of memory, even though the machine has 4GB
> physical (this is under Windows 2000). Even then, we had to modify a
> registry key to be able to use more than 256MB, which is not great for
> end-users.
> 
> Anyway, we're making progress in being able to compile with CL.EXE, but
> we're having trouble with include files. We use the flag
> '-I/home/user/dg/include' to point to the include directory, but it
> can't find it. If we use '-I../include' it works, but for many reasons
> we need to be able to specify absolute paths for include files.
> 
> Has anyone done that ? I was not able to find anything relevant in the
> archives.

I had this same problem to contend with at work.  I'd solved it by
writing a wrapper script around cl that massaged the include list to
match Windows syntax and then invoke the real cl.  It was a but tricky.
I ended up putting the path with my wrapper earlier in $PATH and calling
cl.exe explicitly.  Had to do the same thing with link and lib commands
too.

> Thanks.

-- 
Peter A. Castro <doctor AT fruitbat DOT org> or <Peter DOT Castro AT oracle DOT com>
	"Cats are just autistic Dogs" -- Dr. Tony Attwood


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -