## 02111-1307, USA.
@PROGRAM@: $(@XPROGRAM@_OBJECTS) $(@XPROGRAM@_DEPENDENCIES)
$(@XLINK@) $(@XPROGRAM@_LDFLAGS) $(@XPROGRAM@_OBJECTS) $(@XPROGRAM@_LDADD) $(LIBS)
-CYGWIN @test -n "$(EXEEXT)" && echo timestamp > @PROGRAM@
+## Why take such a funny approach to Cygwin32 executables? Why not
+## just rewrite this file to PROGRAM$(EXEEXT), and then rewrite
+## foo_PROGRAMS similarly? Because then EXTRA_PROGRAMS won't work
+## correctly -- every configure.in will have to know to add $(EXEEXT)
+## when putting a program name into a variable. By doing things this
+## way we can get Cygwin32 support by adding a single macro to
+## configure.in and then re-running automake.
+CYGWIN @test -z "$(EXEEXT)" || echo timestamp > @PROGRAM@
## 02111-1307, USA.
@PROGRAM@: $(@XPROGRAM@_OBJECTS) $(@XPROGRAM@_DEPENDENCIES)
$(@XLINK@) $(@XPROGRAM@_LDFLAGS) $(@XPROGRAM@_OBJECTS) $(@XPROGRAM@_LDADD) $(LIBS)
-CYGWIN @test -n "$(EXEEXT)" && echo timestamp > @PROGRAM@
+## Why take such a funny approach to Cygwin32 executables? Why not
+## just rewrite this file to PROGRAM$(EXEEXT), and then rewrite
+## foo_PROGRAMS similarly? Because then EXTRA_PROGRAMS won't work
+## correctly -- every configure.in will have to know to add $(EXEEXT)
+## when putting a program name into a variable. By doing things this
+## way we can get Cygwin32 support by adding a single macro to
+## configure.in and then re-running automake.
+CYGWIN @test -z "$(EXEEXT)" || echo timestamp > @PROGRAM@