| delorie.com/archives/browse.cgi | search |
Sam Steingold wrote: > > was asking for the actual problem that programmatically accessing the > > cygdrive prefix was supposed to solve. > > I already explained that in > <http://article.gmane.org/gmane.os.cygwin:67856>. > > let me try to do it again: > > unix shell scripts and makefiles do not call cygpath. > when they are used under cygwin, they spit out cygwin pathnames > (/cygdrive/c/...) to non-cygwin programs. How has that got anything whatsoever to do with needing to know the cygdrive prefix? If you want to write a wrapper that converts posix -> windows paths for the sake of non-cygwin programs, you have to convert all paths. It doesn't matter whether a path starts with /cygdrive or not. "notepad /usr/local/foo" fails just as badly as "notepad /cygdrive/c/foo", so the only sane way to do this is to convert all paths. And there are already wrapper scripts that do this, and they surely don't care what the cygdrive prefix is. So I don't see how that addresses the original topic of this thread. Brian -- 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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |