RE: [gnugo-devel] Building GNU Go on Windows

[Ben Lambrechts]

I have build 3.7.11 for windows with mingw and cygwin
You can find the build at http://lithops.sourceforge.net/gnugo.htm

Ben

-----Oorspronkelijk bericht-----
Van: address@hidden
[mailto:address@hidden Namens Gunnar
Farnebäck
Verzonden: zondag 4 november 2007 22:36
Aan: GNU Go development
Onderwerp: [gnugo-devel] Building GNU Go on Windows

Has anybody tried to build GNU Go 3.7.11 on Windows? Does it work?

Whether it does or not the fact remains that the MSVC project files
are a maintenance nightmare. As soon as we add a new source file or a
pattern database file the project files are immediately out of date
and we can only hope that somebody sooner or later notices the problem
and sends in a patch to repair them.

A potential solution to this problem that I want to explore is to use
cmake (http://www.cmake.org) for Windows builds. The main drawback is
that it requires cmake to be installed on the machine where the build
is done but then it generates up to date project files for the chosen
MSVC version, which are used for a completely native build.

The big advantage of using cmake here is that cmake is also available
for GNU/Linux where it instead generates normal makefiles (or kdevelop
project files for those inclined). This means that we can test the
cmake configuration files before committing build changes to CVS,
which greatly improves the chances that building on Windows
continually works.

For various reasons cmake can not be considered as a replacement for
the autotools build system on Unix-type platforms, however. The
supported way to build there will remain ./configure + make (+ make
install).

I have prepared a patch which adds cmake configuration files at
http://trac.gnugo.org/gnugo/ticket/191
They are written by a cmake beginner (me) but suffice for building on 
GNU/Linux and hopefully can be used on Windows.

Please see the ticket for instructions on how to build with cmake. If
you have Windows with MSVC, please give it a try and report how it
worked, or more likely how it failed, so we can fix problems and
evaluate whether this is an effective solution.

/Gunnar


_______________________________________________
gnugo-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnugo-devel