Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <5.1.0.14.2.20021027131018.02d18ee8@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Sun, 27 Oct 2002 13:15:15 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: dmake for cygwin In-Reply-To: <3DBC4223.8080007@beamreachnetworks.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Eric, At 11:44 2002-10-27, Eric M. Monsler wrote: >Vijay Sampath wrote: >>Hi, >> >>Has anybody had any luck compiling dmake for cygwin. Any help is >>appreciated. > >... > >Have you tried the windows dmake from the cygwin shell? When I did so, I >could not figure out how to properly mangle path names such that dmake >knew it was running in a DOS-ish shell. It kept trying to create ksh >files and execute them, rather than .bat files as it did when invoked >under the WinNT command shell. It seemed to be keying on the path >separator of "/" vs. "\" in deciding whether to make .bat or ksh files. I know nothing of dmake, but current versions of the Cygwin utility "cygpath" have both -w / --windows and -m --mixed options. "Mixed" is Windows format with forward slashes. There's also -d, which gives a DOS 8.3 name if the argument names an existing file and -u which produces Unix / POSIX names. If your Windows "dmake" conditions its behavior on path name syntax, this should be enough to control it. >... > >If you do find a way to let dmake play nice under cygwin, please post the >results. > > >Eric Randall Schulz Mountain View, CA USA -- 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/