On March 4, 1999 at 21:26, Stephen Wilson Bailey wrote:
> Amazingly (or not, to you), I've gotten nmh 1.0 to compile and
> actually work (I'm using it now) on Windows NT using the Cygwin32
> B20.1 tool kit.
[snip]
Maybe you can contribute patches that use something like a
#ifdef CYGWIN, or something, to Richard. This way better Cygwin
support can be done incrementally over time. Then the configure
program can set the macro if under CYGWIN.
> Finally, symlinks can't be created, so the installation part of
> commands that are symlinks doesn't work. Furthermore if copies are
What parts of creating symlinks fail? From my observation, Cygwin
supports symbolic links.
> made of the commands which are intended to be symlinked, they still
> fail to recognized the command name properly (because of the .exe, I
> assume, I haven't dug into this yet), and still behave as the basic
> command.
>From my observation, cygwin transparently handles the .exe extension
wrt symlinks. Also, cygwin appears to properly pass the name a program
was invoked as in argv[0]. I guess it could be a problem if the
symlink name containes ".exe". nmh code would probably need to
be modified to also check for ".exe" to deal with Win32 environments.
Note, I had installation problems when I tried to build Gimp under
Cygwin (about a year ago under B19) because of the stupid ".exe"
problem. Unfortunatley, after manually doing the installation, Gimp
would lock up frequently.
--ewh
