>> I know NOTHING about compiling a program, though I'm not a >> disaster with software in general. I'd like to be able to >> build a Windows executable of GNUbg. Could someone provide me >> with clear instructions on how to do this? >> > >I've relied on Jon Kinsey's scripts for this, because I'm in the same >boat as you when it comes to compiling. > >Unfortunately: >A) His web page of instructions has been down since he moved ISP. >B) His scripts are out of date since a recent reorganisation of the >code. They won't compile the latest CVS copy. >C) Jon is on holiday at the moment. > >He has said he will have a look at them when he gets back, when he has >some time. I suggest waiting.
I can try to help here : 1) Download MINGW stuff at http://www.mingw.org/download.shtml and install all of them in the same directory (let's say D:\GNUBG-BUILD\MINGW). I've downloaded only current versions (not candidate ones) : mingw-runtime-3.9.tar.gz binutils-2.15.91-20040904-1.tar.gz mingw-utils-0.3.tar.gz gcc-core-3.4.2-20040916-1.tar.gz gcc-g++-3.4.2-20040916-1.tar.gz mingw32-make-3.80.0-3.exe gdb-5.2.1-1.exe w32api-3.6.tar.gz 2) Download GTK at http://gladewin32.sourceforge.net/modules/news/ and install in the same directory you've installed the MINGW stuff (D:\GNUBG-BUILD\MINGW). I'm currently using : gtk-win32-devel-2.8.18-rc1.exe 3) You may want to install python 2.4.2 (www.python.org). If you don't, it is still possible to compile gnubg with python support (and of course to use python in the compiled gnubg) without installing python : I have to mail you an archive (py2.4.2-include.zip, containing some .h files).Unzip it somewhere (e.g. in the directory D:\GNUBG-BUILD). 4) Download latest (timestamp) snapshot at http://www.acepoint.de/GnuBG/sources/ and unzip the archive in a directory (let's say D:\GNUBG-BUILD\GNUBG-CODE). As an alternative, you can checkout the code from the cvs repository. 5) You need some extra files that are located in 2 separate archives (I can email on request, but one of them is 8Mb) : - addtorepository.zip : some windows-specific files and scripts, - extrafiles.zip : weights, one/two sided databases and some dlls Unzip the content of the two archives somewhere : this will create two directories (addtorepository and extrafiles). Move the content of the two directories into the same directory you unzipped the gnubg sources in (D:\GNUBG-BUILD\GNUBG-CODE) 6) If you want to create windows distribs (I doubt), you have to download InnoSetup (http://www.jrsoftware.org/isinfo.php) 7) You have to declare some environment variables (under Win XP, right click on My Computer, then click on Properties, Advanced, Environment variables) : GNUBG-SOURCE : directory where you have the gnubg code source (in my example, this is d:\GNUBG-CODE) GNUBG-MINGW : directory where you have installed the MINGW/GTK stuff (D:\MINGW) GNUBG-PYTHON : directory where you have installed Python 2.4.2 or, if you didn't install Python, use the directory you've unzipped my python archive in (e.g. D:\GNUBG-BUILD\Python 2.4.2) GNUBG-IS : directory where InnoSetup is installed (optional) 8) If all went ok, you just have to open a DOS shell and go to the directory where the gnubg code is (D:\GNUBG-BUILD\GNUBG-CODE). Check that you have there the 'PythonLib' and 'winbuild' directories (if not, something went wrong). Go into winbuild directory, and run the script 'build_gnubg_all.bat'. This will take a while, but at the end you should have the executables : gnubg-gui-py-sse.exe gnubg-gui-py-sse-debug.exe gnubg-nogui-py-sse.exe gnubg-nogui-py-sse-debug.exe in the D:\GNUBG-BUILD\GNUBG-CODE directory (you can just delete the *-debug.exe ones). The files build-out.txt and build-err.txt contain the compiler output and errors. 9) In order to run them, you must use the 'run-gnubg.bat' script (located in the D:\GNUBG-BUILD\GNUBG-CODE\winbuild directory). Go into that directory and type 'run-gnubg.bat gnubg-gui-py-sse.exe'. That should do it. MaX. P.S. the ones insterested in doing this, please email me directly so that I can mail you the 3 necessary archives. P.P.S. Useful to sort out DLL problems : http://www.dependencywalker.com/ _______________________________________________ Bug-gnubg mailing list Bug-gnubg@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnubg
