This is the mail archive of the
mailing list for the Cygwin project.
Re: Various questions - docs, paths
- To: John S Cooper <John dot Cooper at eu dot citrix dot com>
- Subject: Re: Various questions - docs, paths
- From: Corinna Vinschen <corinna at vinschen dot de>
- Date: Thu, 27 Apr 2000 14:42:45 +0200
- CC: cygwin at sourceware dot cygnus dot com
- References: <uvh13kiu3.fsf@KONTIKI.cam.eu.citrix.com>
- Reply-To: cygwin at sourceware dot cygnus dot com
John S Cooper wrote:
> o The FAQ and User's Guide seem to refer to B20 -- are there equivalent docs
> for the new 1.1.0, or does everything in the older docs still apply?
The new FAQ is work in progress.
> o What's the deal with these new "/cygdrive" path prefixes?
> | bash-2.03$ type bash
> | bash is /cygdrive/h/cygnus/bin/bash
/cygdrive is the standard prefix for paths which are
unresolvable via the mount table.
> They don't seem to appear in my mount table:
That's logical because you create the mount table by yourself
whereas /cygdrive is used automagically.
> o We have a Makefile that needs to pass the current directory to a (non-cygwin)
> program. If we use $PWD, we get the /cygdrive style path, which the program
> doesn't grok. Do I have use conditionally (our Makefile also runs on Linux)
> call cygpath to convert to Windows style paths in all places we invoke this
AFAICT, yes, indeed.
> o Is there a way to tell cygwin to always use Windows style paths (with drive
> letters) rather than the "unix" paths that are only understood by other
> cygwin programs?
No. Cygwin is a POSIX layer. On the other hand cygwin doesn't complain
if you use sth like 'C:\\foo\\bar\\baz' on the command line.
> o I've seen people allude to a CYGWIN variable -- where is this documented?
Umm, let's see... ah, ok here we go:
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org