Added a README for building the win32 cross compiler.

First stab at a c172 flight model contributed by Tony Peden.

diff --git a/Makefile.am b/Makefile.am
index 6747942934eb1130eeb0aa46f176a552e32e7cb7..8bebcb56e2c4ded6830ce295f640add37730515e 100644 (file)
--- a/Makefile.am
+++ b/Makefile.am
@@ -1,8 +1,8 @@
 SUBDIRS = Include Lib Simulator Tools Tests
 
 EXTRA_DIST = FG-FAQ.v3 README.Unix README.Linux README.MacOS README.Win32 \
-       README.autoconf README.gfc README.gpc README.plib README.running \
-       Thanks VERSION acsite.m4 acconfig.h irix-hack.pl
+       README.Win32-X README.autoconf README.gfc README.gpc README.plib \
+       README.running Thanks VERSION acsite.m4 acconfig.h irix-hack.pl
 
 dist-hook:
        tar cf - Hints | (cd $(distdir); tar xvf -)

diff --git a/README.Win32-X b/README.Win32-X
new file mode 100644 (file)
index 0000000..18ba457
--- /dev/null
+++ b/README.Win32-X
@@ -0,0 +1,85 @@
+http://www.cygnus.com/ml/gnu-win32/1998-Nov/0177.html
+
+Building cross cygwin b20 tools [Re: Linux->Win32 cross
+compiler ?]
+
+Mumit Khan (khan@xraylith.wisc.edu)
+Wed, 4 Nov 1998 09:38:23 -0600 (CST) 
+
+      Messages sorted by: [ date ][ thread ][ subject ][ author ] 
+      Next message: Austin David France: "RE: B20 & bash 2.02.1(2) broken" 
+      Previous message: Neil Schemenauer: "Bash exits after background command exits (B20)" 
+      In reply to: Felix E. Klee: "Linux->Win32 cross compiler ?" 
+      Next in thread: Peter Dalgaard BSA: "Re: Linux->Win32 cross compiler ?" 
+
+On Mon, 2 Nov 1998, Felix E. Klee wrote:
+
+> Hi,
+> 
+> does anyone know if a cross compiler exists for Linux which
+> creates Win32 executables just like gnuwin32 does?
+> 
+
+============ building CROSS
+
+You can always build one yourself. Download the CDK source, and do the
+following:
+  
+  $ mkdir /cygwin-b20
+  $ cd /cygwin-b20
+  $ tar zxvf /tmp/dev-src.tar.gz
+  $ cd src
+  $ mkdir CROSS
+  $ cd CROSS
+  $ ../configure --prefix=/usr/local/cygb20 --target=i386-cygwin32 -v
+  $ make > make.log 2>&1
+  [ check for errors . If OK ]
+  $ make install > install.log 2>&1
+
+After you're done, add it to path (if you're using a bourne-shell
+compatible, otherwise use csh syntax).
+  
+  $ export PATH=$PATH:/usr/local/cygb20/bin
+  $ i386-cygwin32-gcc -v
+  [ should report egcs-1.1 etc ]
+
+All the binaries for i386-cygwin32 target are prefixed with i386-cygwin32-
+prefix.
+
+============ building NATIVE tools using CROSS tools just built.
+
+Now if you want to build native tools on eg., a i686-pc-linux-gnu box with 
+the same pathnames that wCygnus uses:
+
+  $ cd /cygwin-b20/src
+  $ mkdir NATIVE
+  $ cd NATIVE
+  $ ../configure --prefix=/Cygnus/cygwin-b20 \
+    --exec-prefix=/Cygnus/cygwin-b20/H-i586-cygwin32 \
+    --target=i386-cygwin32 --host=i386-cygwin32 \
+    --build=i686-pc-linux-gnu -v
+  $ make > make.log 2>&1
+  [ check for errors . If OK ]
+
+Now of course, you want to install it to a *DIFFERENT* location than
+/Cygnus/cygwin-b20 on your Unix host before creating an archive to
+copy to a Cygwin box. Let's say you first install it to /tmp/cygwin.
+
+  $ make prefix=/tmp/cygwin exec_prefix=/tmp/cygwin/H-i586-cygwin32 \
+    install > install.log 2>&1
+  $ cd /tmp/cygwin
+  $ tar zcvf /tmp/dev-cygwin-b20.tar.gz .
+
+Copy /tmp/dev-cygwin-b20.tar.gz to your Cygwin box and unpack:
+  
+  [win32]$ cd /Cygnus/cygwin-b20
+  [win32]$ tar zxvf /tmp/dev-cygwin-b20.tar.gz
+
+Regards,
+Mumit
+
+
+-
+For help on using this list (especially unsubscribing), send a message to
+"gnu-win32-request@cygnus.com" with one line of text: "help".
+

diff --git a/Thanks b/Thanks
index f00d40c8bef26b515926faf97a4a5478c327dfb8..fd2ea138a0fc4087ea6836913a256c6c653a87db 100644 (file)
--- a/Thanks
+++ b/Thanks
@@ -195,6 +195,10 @@ Chris Schoeneman <crs@millpond.engr.sgi.com>
   will have an influence on the development of our own audio library.
 
 
+Phil Schubert <philings@zedley.com>
+  Contributed various textures.
+
+
 Jonathan R Shewchuk <Jonathan_R_Shewchuk@ux4.sp.cs.cmu.edu>
   Author of the Triangle program.  Triangle is used to calculate the
   Delauney triangulation of our irregular terrain.

diff --git a/configure.in b/configure.in
index 54f511fb992c74a6c0f4e009ce985095c59db696..93b9ee97b896ce55db8b35a2ce43718bb85bdb3e 100644 (file)
--- a/configure.in
+++ b/configure.in
@@ -51,14 +51,14 @@ if test "x$with_efence" = "xyes" ; then
 fi
 
 dnl specify the compiled flight model
-AC_ARG_WITH(flight-model, [  --with-flight-model=xxx Specify the flight model (navion, cherokee)])
+AC_ARG_WITH(flight-model, [  --with-flight-model=xxx Specify the flight model (navion, c172)])
 
-if test "x$with_flight_model" = "xcherokee" ; then
-    echo "Building with cherokee flight model"
+if test "x$with_flight_model" = "xc172" ; then
+    echo "Building with c172 flight model"
 else 
     echo "Building with navion flight model"
 fi
-AM_CONDITIONAL(ENABLE_CHEROKEE, test "x$with_flight_model" = "xcherokee")
+AM_CONDITIONAL(ENABLE_C172, test "x$with_flight_model" = "xc172")
 
 dnl Let the Win32 user specify if they want to build with the SGI
 dnl opengl.dll as opposed to the more standard openg32.dll