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 in
18 windows explorer. Be sure to read this package's README :
20 http://www.cygnus.com/misc/gnu-win32/readme_toc.html
22 After installing the cygnus compiler and the usertools you should
23 find a program group "Cygnus" in your start menu.
25 2. Install the Silicon Graphics OpenGL dynamic link libraries. For
26 this purpose, get the file sgi-opengl2.exe from the flight gear
27 project site. This is a win95/winnt self extracting installation
28 program. Install it by double-clicking in windows explorer.
30 3. Fetch the Flight Gear code and special Win32 libraries. These can
33 http://www.menet.umn.edu/~curt/fgfs/Downloads/Source/
35 Grab the latest "FlightGear-X.XX.zip" and "win32-libs-X.XX.zip"
38 4. Unpack the FG source code. Run:
40 pkunzip -d FlightGear-X.XX.zip
42 Be sure to use the -d option. This will create all the needed
43 subdirectories. Otherwise you will have one big mess! Trust me!
45 5. Change to the newly created FlightGear-X.XX directory and unpack
46 the Win32 libraries. Run:
49 pkunzip -d win32-libs-X.XX.zip
53 You will find a file called "install.exe" In the Win32 directory
54 created when you unzip the win32-libs-X.XX.zip file.
56 This version of install.exe should replace the one in your
57 H-i386-cygwin32\bin directory - it's sole claim to fame is that it
58 "understands" that when many calls to it say "install foo" they
59 mean "install foo.exe". If you skip this step, and attempt an
60 install with the older version present, "make install" will fail.
62 Side Note: we need to make a distinction between the "build tree" and
63 the "install tree." The "build tree" is what we've been talking
64 about up until this point. This is where the source code lives
65 and all the compiling takes place. Once the executables are
66 built, they need to be installed someplace. We shall call this
67 install location the "install tree". This is where the
68 executables, the scenery, the textures, and any other run-time
69 files will be located.
71 7. Configure the make system for your environment and your "install
72 tree". Tell the configure script where you would like to install
73 the exectuables and all the scenery and textures by using the
74 "--prefix" option. In the following example the base of the
75 "install tree" is "/FlightGear". Run:
77 ./configure --prefix=/FlightGear
79 8. Build the executable. Run:
83 9. Create and populate the install tree. Run:
87 currently this step fails, but I hope to find a solution soon.
88 You can probably install everything by hand for now ... for example:
90 cp Simulator/Main/fg.exe /FlightGear/bin/fg.exe
91 cp Simulator/Main/runfg.bat /FlightGear/bin/runfg.bat
93 Important Note: so far you've built and installed the simulator and
94 related tools. Before you can actually try it out, you need to
95 make sure you have the appropriate scenery and texture downloaded
96 and unzip'ed in your "install tree".
98 10. Download and install the scenery and texture files.
100 11. Set the runtime environment variable to point to the base of your
103 export FG_ROOT=/FlightGear
105 12. Try it out! There are several ways to run flight gear once it has
106 been installed. The simplest is as follows. Run:
108 /FlightGear/bin/runfg.bat
110 13. I appreciate feedback. Tell me if it works! If it doesn't, tell me
111 what went wrong. My email is curt@me.umn.edu