Re: [gnugo-devel] Compiling GnuGo

[bump]

> Does anybody know exactly how the 'configure' script and 'makefile' 
> work in relation to GnuGo.  I know that the configure script generates 
> a header file, and the makefile seems to be fairly standard- however 
> after looking through both of them, they seem needlessly complicated.  
> Against the 'if it ain't broke...' argument, would it be a good idea to 
> replace these files?  To help unclutter the root directory and make it 
> easier to create a project file for IDEs such as KDevelop or 
> ProjectBuilder?  Are these scripts standard for many other GNU projects?

This is the standard result of using GNU autoconf and automake. It
works pretty well for portability.

The files configure and Makefile.in (in each directory) are automatically
generated by autoconf and automake. The only files you should ever need
to look at are configure.in and Makefile.am.

Dan