According to Jim Meyering on 1/13/2010 3:19 AM: > I didn't account for that use case. > I wonder if there is some way to write/use a command-not-found > handler to automate the error-prone "add-$EXE-suffix" at run-time. > > If at all possible, I would like to avoid the invasive change > of adding the $EXE suffix to every just-built-binary invocation > in every test script.
mingw and cygwin handle it just fine, but my reading (although not my experience) seems to imply that BeOS requires the .exe suffix. Wine is another case where the suffix is (currently) important. But I do agree that it would be much nicer if wine could do things automatically rather than appending EXE in all of gnulib. > If the $EXE suffix is not required in that particular case, > an alternative would be to create a temporary directory, D, > and populate it with links of the form program ->../.../program.exe > (or simply copies, if ln isn't an option) and then prepend "D:" to PATH. Hmm. It would have to be done with care. On cygwin, you can't (easily) create both foo and foo.exe in the same directory, so it would have to be via separate directories. And on mingw, there are no symlinks, but copies of an executable without an .exe suffix are unlikely to be run. -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net
signature.asc
Description: OpenPGP digital signature
