|
From: Tor L. <tm...@ik...> - 2010-04-16 08:33:34
|
> Hadn't thought of that. Not sure why it would be hard to do, though. You know the saying, "are you volunteering"? But seriously, MSYS paths that differ wildly from native Windows path are not really something that can be recommended. The purpose of MSYS is not to provide an immersive Unix emulation environment that would make you forget you are actually on Windows. Especially as the point in MSYS is to assist in developing native Windows applications that don't know anything about MSYS. MSYS paths are just a minor convenience, and only required by some configure scripts etc that could get confused by Windows paths with drive letters. One is expected to be aware all the time what the corresponding underlying Windows paths are, and fluently be able to use either form depending on context. If one is using very "deep" MSYS mounts that make MSYS paths differ wildly from corresponding Windows paths, one is doing something wrong. (Yeah, so for paths inside the MSYS installation tree itself, typically rooted at c:\msys\1.0 , the paths do differ quite a bit. But at least I don't put anything of my own stuff in the MSYS tree, but in separate trees, which have very similar paths both in Windows and MSYS forms. Like c:\devel and /devel, or c:\opt and /opt.) All the above is just my humble opinion, of course. --tml |