Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <37B8CBB1.B5773755@comco.com> Date: Mon, 16 Aug 1999 21:40:49 -0500 From: Tadeusz Liszka Organization: Computational Mechanics, Inc. X-Mailer: Mozilla 4.07 [en] (X11; U; IRIX 5.3 IP22) MIME-Version: 1.0 To: Kevin Hill CC: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Make quoted strings problem running from cmd.exe... References: <37B8BF1A DOT D6E06EA0 AT bigfoot DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kevin Hill wrote: > > Dear reader, > > I have Cygwin b20.1 (including make version 3.75) and NT4.0 sp4. I am > trying to use make from within the normal cmd.exe of NT, rather than > from within any of the cygwin shells. The problem I have ONLY happens > when I run from cmd.exe; it works find from within sh. ....... Don't blame it on make - it is cmd.exe doing. Once shell parses the inputline, make does what it can. cmd.exe is too stupid to properly interpret quotes "" like true shell. Write small code and test VC++ and Cygwin gcc and see what actually is processed by cmd/shell and what comes to your code. I suspect that cmd passes quotes, and nmake compensates for it. It is consistent with DOS/NT/Win32 philosophy where each program is responsible for interpreting *.*, and cmd.exe simply passes them down. -- Tadeusz :: The public opinion should be alarmed by its own nonexistence :: (512)467-0618 ext. 526 :: Stanislaw J. Lec, trans. TJL -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com