public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Earnie Boyd <earnie@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: cygwin_conv_path strange behavior
Date: Wed, 27 Jun 2012 12:11:00 -0000	[thread overview]
Message-ID: <CA+sc5mmhidv4O=ASd=Azu_X1Aarg977QnQOJ+uejAvo5AFkN+A@mail.gmail.com> (raw)
In-Reply-To: <CAO1jNwv-TEEZfLTvtZxdQ3oa9k+KsHMaM8v6sLx-TZxN73OumA@mail.gmail.com>

On Wed, Jun 27, 2012 at 7:59 AM, Jan Nijtmans wrote:
>
> Now, copy cygwin1.dll to the same directory
> as mypath.exe, and do the same
> from a cygwin shell, it prints:
>    $ ./mypath
>    win32 path: C:\some\path\foo\mypath.exe
>    posix path: /cygdrive/c/some/path/foo/mypath.exe
> From a win32 command shell:
>    > .\mypath
>    win32 path: C:\some\path\foo\mypath.exe
>    posix path: /foo/mypath.exe
>

This sounds it is as expected.  You copied only cygwin1.dll so the
shell you started had a cygwin1.dll in another directory so that / is
mapped to the parent directory containing the cygwin1.dll the shell is
using.  However, when you use the win32 command shell there is no
previous mapping of / to the parent directory containing cygwin1.dll
so / is mapped to c:/some/path and the function correctly reports
/foo/mypath.exe.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

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

  reply	other threads:[~2012-06-27 12:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 11:59 Jan Nijtmans
2012-06-27 12:11 ` Earnie Boyd [this message]
2012-06-27 12:29   ` Jan Nijtmans
2012-06-27 12:30 ` Corinna Vinschen

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='CA+sc5mmhidv4O=ASd=Azu_X1Aarg977QnQOJ+uejAvo5AFkN+A@mail.gmail.com' \
    --to=earnie@users.sourceforge.net \
    --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).