Re: cygwin1.dll incluson in Cygwin makefile

[Paul Newell <pnewell at cs dot cmu dot edu>]

Christopher:

Thanks for the very prompt reply. I tried both and they worked as 
expected. I was expecting  the opening quote to match to the closing 
just like I had issued it in dos in a cmd window (where cmd /c dir "c:\" 
works as expected). Regardless, thanks for straightening me out on this.

I thought I checked /cygdrive and found them empty (though mount said 
otherwise). Given how long it took the "ls /cygdrive" to come back with 
something, I guess I might have controlC-ed out. I notice that cmd /c 
dir from the "/" gives me what I would expect, but cmd /c dir \cygdrive 
doesn't show me the c and f drive, so I just got confused as I wasn't 
looking the right way. As in your paragraph about "still missing the point"

I agree that I'm looking at it the wrong way given moving legacy Windows 
code under Borland over to Cygwin. And this thread is proving to be a 
good way to learn just how wrong it is. That being said, I probably 
wouldn't "get it" without going through the exercise  ... failure is a 
great and humbling teacher.

Once again, thanks to you and Brian for the help,
Paul

Christopher Faylor wrote:
> On Mon, May 26, 2008 at 07:26:00PM -0700, Paul Newell wrote:
>   
> > cmd /c dir "c:\"
> >
> > just generates a shell that I have to controlC out of (other variants
> > caused me to find you 2004 posting when I had to hit enter a second
> > time).
> >     
>
> It's not a shell.  It's a continuation line.  \ is a quoting character
> on linux-like systems.  So the above says "quote the next character",
> meaning that the " character is not recognized as closing the previous
> ".  If you had typed another " you would have seen output from your dir
> but if you really need to use a backslash then use \\.
>
> But, I think you're still missing the point that the main focus of
> Cygwin is to be a POSIX like environment.  You shouldn't need to revert
> to cmd for anything.  If you need to reference other drives then you
> can use /cygdrive/c/foo rather than c:\foo .
>
>   
> > As for distributing my code ...  that isn't the intent at all.  This is
> > nothing more than trying to learn for myself how to make better use of
> > cygwin for personal uses.  I've been using cygwin since the Win98se
> > days but always in a very limited form and always running a Borland
> > compiler on the Win98 machine.  I'm trying to teach myself what I need
> > to know to just run cygwin on Windows and Fedora / RedHat on Linux ...
> > skipping Windows compilers altogether.
> >     
>
> If you are skipping Windows compilers then you definitely don't want to
> use the c: or \ notation.  Stick to "forward slashes" and no colons when
> using cygwin programs.
>
> cgf
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>
>
>   


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/