4 Here is a quick outline of *one* way you can build FG for Win32 using
5 a completely free development environment.
7 1. Install and configure the Cygnus Gnu-Win32 development
8 environment. The latest version is Beta 19. The main
9 Cygnus Gnu-Win32 page is at:
11 http://www.cygnus.com/misc/gnu-win32/
13 You can download the Cygnus Gnu-Win32 compiler from:
15 ftp://ftp.cygnus.com/pub/gnu-win32/latest/cdk.exe
17 To install, just run the file: "cdk.exe" by double-clicking on it
18 from windows explorer. Be sure to read this package's README:
20 http://www.cygnus.com/misc/gnu-win32/readme_toc.html
22 and install them as well. After installing the cygnus compiler
23 and the usertools you should find a program group "Gygnus"
27 2. Fetch the Flight Gear source code and win32 libs. They can be
30 http://www.menet.umn.edu/~curt/fgfs/Downloads/
32 Grab the latest source-X.XX.zip file.
34 In addition, you need the win32 libraries from win32-libs-X.XX.zip
36 Also, don't forget to download scenery and textures. These aren't
37 needed to built the code, but you'll need them before you can run
40 3. Unpack the FG prototype code and the libraries. Run:
44 Be sure to use the -d option. This will create all the needed
45 subdirectories. Otherwise you will have one big mess!
47 This should create a directory called ``FlightGear'' with several
48 subdirectories. Do the same with the libraries.
51 4. The win32-libs zip file provides the necessary OpenGL/GLUT headers
52 and libraries for the build process.
54 Before trying to run the executable, you should copy glut.dll from
56 ...\FlightGear\Win32\glut.dll
58 into someplace in your path such as:
60 ...\FlightGear\Src\Main\glut.dll
63 5. Install the Silicon Graphics OpenGL dynamic link libraries. For
64 this purpose, get the file sgi-opengl2.exe from the flight gear
65 project site. This is a win95/winnt self extracting installation
66 program. Install it by double-clicking in windows explorer.
69 6. Edit the ``commondefs'' file, if necessary. Go to the main
70 FlightGear source directory. From where ever you extracted the FG
71 code, cd to ``FlightGear\Src''. Edit the file called
72 ``commondefs''. Find the part of the file that says: ``Uncomment
73 one of the following sections depending on your system''
75 Uncomment all the makefile defines in the ``Cygnus Win32 beta19''
76 section. Also, you should comment out any of the defines in the
77 other platform dependent sections. Depending on the version,
78 you may find, that the appropriate settings are already done
79 and you can skip this step.
82 7. Prepare the shell. Call the Cygnus shell from the start menu.
83 At first, you have to mount your flight gear drive (assuming it is g:)
88 (Be careful writing slashes; you are working within a strange mixture
89 of DOS/WIN95/UNIX here.)
91 If anything went wrong with mounting you can unmount the drive with
94 Now change to the flight gear source directory with
96 cd /mnt/FlightGear/Src
98 (make sure you're correct with the "pwd" command)
101 Next, you have to set the environment variables as:
103 SET FG_ROOT=/mnt/FlightGear
104 SET FG_ROOT_SRC=${FG_ROOT}/Src
105 SET FG_ROOT_LIB=${FG_ROOT}/Lib
108 8. Build the executable. Type first
112 and after that's done type
116 You will see a few warning messages from the compiler, but none of
119 Be prepared flight gear to need 10 minutes or more for compilation
120 (depending of your system).
123 9. Try it out! When make is done close the Cygnus shell. There are several
124 possibilities running flight gear. The one which should always work
127 Open an ordinary DOS shell. Within this one reset the flight gear root
128 environment variable to
130 SET FG_ROOT=g:\flightgear
132 (or whatever your drive is.) This is absolutely necessary as win95
133 does not recover your "mounted" drive.
135 Goto the directory where your freshly build executable sits, i.e.
137 cd g:\flightgear\src\main
142 10. Tell me that it works! If it doesn't, tell me what goes wrong. My
143 email is curt@me.umn.edu. Please send me email and let me know
144 what changes need to be made to this document and these procedures
145 to make them easier to understand and follow.