|
From: Earnie B. <ea...@us...> - 2004-10-27 12:54:44
|
Posted on DATE by AUTHOR Guy Gascoigne - Piggford > True, but part of the problem is that if you try to build from within > Msys, it actually looks like it's working, only to break in an obscure > way after having got off to a good start. > > If it just didn't work in the first place it might have been less > confusing. :) > > Guy > Guy, I'm in favor of finding a solution. I will take a look at the emacs build process see how the path translation can be modified. Which version of MSYS are you using? Sorry if you've given that information before. > Fred Kunz wrote: > >>Without either arguing for or against a path conversion option, it might >>be appropriate to point out that there are two easy ways to build emacs >>on Windows without either CYGWIN or MSYS. One is to use Visual C++ >>environment with some GNUWin32 modules and the other is to use a MinGW >>environment with some GNUWin32 modules and configure and build from the >>emacs\nt directory. This includes the current CVS tree with image >>support. >> Fred, Are you saying that there is a special build method for MinGW beyond configure && make? I don't like that method as it causes someone to have to make changes when the package structure changes. I very much like the automated features of the auto tool set of modules. Please encourage its use for MinGW builds as well. Earnie |