Re: Relative vs. Absolute path problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Patrick Herbst on 1/31/2007 6:07 AM: > from your home directory ../../../ = one level up from the cygwin root. One level up from cygwin root is still cygwin root. /.. == / as required by POSIX. - -- Don't work too hard, make some time f

Re: Relative vs. Absolute path problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Stephen Henry on 1/31/2007 2:50 AM: > > This works perfectly (from a directory in my home directory): > $ ./x264.exe -o out.h264 ../../../testseq/yuv420/COASTGUARD-YUV420-CIF > 352x288 > > Whilst this does not: > ./x264.exe -o out.264 /t

Re: Relative vs. Absolute path problem

from your home directory ../../../ = one level up from the cygwin root. for example... if home is c:\cygwin\home\user then that relative path would put you at c:\ the root (/) for cygwin is actually the cygwin directory (c:\cygwin) if you're trying to get just on your c:\ you have to specify it

Relative vs. Absolute path problem

Hi, I have a really strange problem with my Cygwin installation. It concerns a filename parameter given to a application launched from the bash command prompt. The problem is as follows: I have an application that takes a filename parameter. The application uses the 'fopen' command to open the f