This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Problems with path resolution

On Tue, Aug 28, 2001 at 05:46:18AM +0800, bumps man wrote:
>-----Original Message-----
>From: "Gerald W. Shapiro" <>
>Date: Mon, 27 Aug 2001 14:10:38 -0400 (EDT)
>Subject: RE: Problems with path resolution
>> I just joined this list, and my question seems similar to Dan's. And
>> perhaps it is a mingw group question, but here I go... joining the hoards
>> of ignorant newbies bothering the list
>> In one of the gprolog makefiles an auxiliary program takes a path
>> and a filename as input. Built with cygwin1.dll, fopen() in the auziliary
>> program has no problem finding /usr/local/blahblah/foo.h , but using
>> -mno-cygwin, the same is not found. If I run the no-cygwin version outside
>> the makefile, and provide a relative path, it works fine, but the
>> no-cygwin version does not recognize the full unix-style path.  My cygwin
>> installation root is c:\cygwin. 
>> Is there something dreadfully obvious that I am missing here?
>> Gerald
>I used to have similar issues with pathnames.  They were resolved when
>I made my root e:\ instead of e:\something\else.
>A non-cygwin Win32 app doesn't understand your cygwin root.

This is the answer to this issue.  Cygwin doesn't affect path
recognition in non-cygwin applications.  Use the cygpath program to
translate paths to Windows form or if an "identity" mount arrangement is
acceptable then that is another alternative.


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]