From: Joerg B. <jo...@sq...> - 2002-11-26 11:48:01
|
Hi! "Mehul N. Sanghvi" wrote: > > [...] > My problem seems to be that make/gcc/g++ etc. do not seem to be > following symbolic links. [...] AFAIK, no variant of Windows really supports "symbolic links" in the general sense known from all current Unix variants (+ Linux). They have those ".lnk" shortcuts to call a program and supply it with arguments, but they do not support the name resolution of a symbolic link somewhere within a path name. As a consequence, AFAIK you can not have a symbolic link pointing to a directory. > > Now if I replace TOP with an actual directory called TOP, and then > actually copy the include directory and its contents into the > actual TOP directory, then everything works fine. To be expected - normal path name resolution. > > If I keep TOP as a symbolic link, then only cygwin tools seem to > work correctly. I am doing all of this from inside of Cygwin bash > shell. IMO this is due to the fact that they use their own runtime library and _not_ the Windows libraries. Whatever CygWin creates for you, Windows (runtime, API, ...) does not recognize it as a "symbolic link". Check with the Windows "Explorer" - is it shown / handled as a directory? > > I have tried both MinGW-2.0 and MinGW-1.1 and get the same > results. I didn't find much by way of the FAQ. Is this a known > problem ? Does anyone have pointers/suggestions ? Works as designed (in Redmond). Regards, Joerg Bruehe -- Joerg Bruehe, SQL Datenbanksysteme GmbH, Berlin, Germany (speaking only for himself) mailto: jo...@sq... |