> Date: Wed, 22 Oct 2014 08:11:07 +0200 (CEST) > Cc: groff@gnu.org > From: Werner LEMBERG <w...@gnu.org> > > - in `m4/groff.m4', add a function named `GROFF_MINGW_CMD_FILES' or > the like that defines the variables `make_winscripts', > `make_install_winscripts', and `make_uninstall_winscripts', which > hold the make targets `winscripts', `install_winscripts', and > `uninstall_winscripts', respectively, depending on the platform > > - add `GROFF_MINGW_CMD_FILES' to `configure.ac' > > - in `Makefile.in', add the triplet > > make_winscripts=@make_winscripts@ > make_install_winscripts=@make_install_winscripts@ > make_uninstall_winscripts=@make_uninstall_winscripts@ > > and insert those three values to `MDEFINES' > > - add the `arch/mingw' directory to the `OTHERDIRS' variable in > `Makefile.in'. > > - put a `Makefile.sub' file into `arch/mingw'; you might use > e.g. `contrib/eqn2graph/Makefile.sub' as template, with the > necessary dependency stuff as for `xxx_htmldoc' in > `doc/Makefile.sub' > > WINSCRIPTS = foo1.cmd \ > foo2.cmd \ > ... > > all: $(make_winscripts) > install_data: $(make_install_winscripts) > uninstall_sub: $(make_uninstall_winscripts) > > winscripts: $(WINSCRIPTS) > > install_winscripts: $(WINSCRIPTS) > ... install stuff ... > > uninstall_winscripts: > ... uninstall stuff ...
Thanks, but this is too much work for too little benefit. Especially since you are going to switch to autotools very soon, and then all this would have to be rewritten anyway. Would it be acceptable to have in arch/mingw/Makefile.sub the install and uninstall targets which on systems other than MinGW/MSYS will do nothing?
