From:	pvogel AT chromatic DOT com (Peter A. Vogel)
Subject:	RE: nmake and '\' style path ...
7 Dec 1998 19:23:10 -0800 :
Message-ID:	<000a01be2204$b4ab6ea0$edd110ac.cygnus.gnu-win32@capsela.chromatic.com>
References:	<19981207032753 DOT 9513 DOT qmail AT findmail DOT com>
Mime-Version:	1.0
To:	"Song Jin" <sojin AT uta DOT edu>, <gnu-win32 AT cygnus DOT com>

\ is an escape character to the cygnus shell (like it is to all
true shells).  Hence if you want a literal backslash, you must use
two backslashes.

More to the point, if you are going to use the cygnus shell, you 
should use the cygnus make (or your own compilation of gnumake)
which understands forward slashes.  Do not use that horrible 
excuse for a make utility that Microsoft foists on unsuspecting
developers as a way to reduce their productivity.

-Peter

> -----Original Message-----
> From: owner-gnu-win32 AT cygnus DOT com [mailto:owner-gnu-win32 AT cygnus DOT com]On
> Behalf Of Song Jin
> Sent: Sunday, December 06, 1998 7:28 PM
> To: gnu-win32 AT cygnus DOT com
> Subject: nmake and '\' style path ...
> 
> 
> I have played with gnuwin32 for just a little bit 
> more than a month. The make works smoothly, yet I can get nmake 
> working properly. The problem I have
> been confronting is that the '\' style path seems
> not being recognized by the shell - I assigned env
> var to maintain the path info required by nmake. I set the 
> 'MAKE_MODE' to win32 already. It seems 
> to me the shell always discard the '\' in path env var, and 
> complain the executables cannot be found. Could anyone give me 
> advice on solving the problem? I would appreciate. Thanks in advance.
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
> 
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -