public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Randall R Schulz <rrschulz@cris.com>
To: cygwin@cygwin.com
Subject: Re: dmake for cygwin
Date: Sun, 27 Oct 2002 17:09:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20021027131018.02d18ee8@pop3.cris.com> (raw)
In-Reply-To: <3DBC4223.8080007@beamreachnetworks.com>

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/

      reply	other threads:[~2002-10-27 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-27  1:01 Vijay Sampath
2002-10-27 10:06 ` George William Smith
2002-10-28  4:28   ` Peter A. Castro
2002-10-27 15:15 ` Eric M. Monsler
2002-10-27 17:09   ` Randall R Schulz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.2.20021027131018.02d18ee8@pop3.cris.com \
    --to=rrschulz@cris.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).