Juanma Barranquero wrote:
The problem is, I don't think that checking tools is a good strategy,
on the long term. Different versions sometimes work or cease to work.
I was able to build the Emacs info files with Cygwin for a while, and
after some update or other the thing failed. Me, I've assembled a .ZIP
with the tools needed (except MinGW, which I install separately), and
I unzip it wherever I want to compile Emacs. They are completely
separated of other installations of Unix tools that I may have on my
computer, and for sure I don't intend to change anything inside it
unless a future Emacs requires an upgrade (as Jason said, that
sometimes happens with make-info).
Maybe different strategies are needed for different times. I have
noticed the careful notes in INSTALL about certain parts of the tools.
Perhaps that could be extended a bit. I see three different current tool
packages on w32: GnuWin32, CygWin and MSYS+MinGW. I am not sure about
UnxUtilites, are they maintained? Staying with one of those for a
particular purposes may be the best.
In my case I have decided to go with GnuWin32+MinGW when building Emacs.
For run time program I am thinking about using MSYS instead since
sometimes sh is needed. (However I have not been able to build with
MSYS.) I've learned the hard way you should not mix the tools so if I am
using MSYS I make sure I put that first in the path (for example by
using (add-to-list <msys-path> 'exec-path) in Emacs). Currently I have
MSYS installed, but it is not on my path (except for sometimes inside
Emacs).
I never noticed any programs named "info" or "install-info" was needed
when doing this. What are you referring to?
Sorry, info is not needed, I think. install-info is. Look at
nt/multi-install-info.bat.
Eh, sorry too. I have it, the installation packages from GnuWin32 works
rathers seemlessly ;-)
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
