From: Eli Z. <el...@gn...> - 2011-12-26 17:09:14
|
> Date: Mon, 26 Dec 2011 10:15:59 -0500 > From: Earnie <ea...@us...> > > Use --prefix=`cd /mingw && pwd -W` instead of --prefix=/mingw to get the > windows absolute value. Thanks. But this will probably bite me elsewhere, since the configure script will need to DTRT with d:/foo/bar style of file names, which will at least sometimes fail. After all, MSYS uses /d/foo/bar for a good reason, doesn't it? > The problem though still exists since on Windows the user chooses > where to install /mingw in the Windows path hierarchy. Sorry, I didn't understand this comment. > >> You can hardcode a relative path (which might be "/"-separated just as > >> well) and then construct the full path from it and some prefix > >> (usually - executable module directory, with some clever detection of > >> the fact that it might be in /bin subdirectory). > > > > Groff does this automatically: e.g., it prepends the directory where > > its executable lives to PATH. > > > > You mean before it spawns child processes? Yes. The code that spawns already searches PATH with that directory prepended to it. > LRN's suggestion is to create a program to simply print the argument > passed to it which in the case of a path would be the converted to > Windows path. Yes, I understand that. But that, too, requires hacking some Makefile or script, and OTOH editing these file names with Sed is trivial, so I don't think LRN's suggestion is particularly better. It does avoid the need to use Sed, but Sed is a necessary part of any working MSYS installation anyway. Thanks. |