From c2e4e46546ea6a7261259afa630e5d7dc46bdf7d Mon Sep 17 00:00:00 2001 From: James Turner Date: Wed, 18 Nov 2020 17:31:02 +0000 Subject: [PATCH] Remove docs from the dawn of time. All of these are subsumed by CMake these days, hurrah. --- docs-mini/README.Cygwin | 25 -------- docs-mini/README.IRIX | 73 ---------------------- docs-mini/README.MSVC | 131 --------------------------------------- docs-mini/README.MacOS | 33 ---------- docs-mini/README.Win32-X | 85 ------------------------- docs-mini/README.mingw | 109 -------------------------------- docs-mini/README.plib | 16 ----- 7 files changed, 472 deletions(-) delete mode 100644 docs-mini/README.Cygwin delete mode 100644 docs-mini/README.IRIX delete mode 100644 docs-mini/README.MSVC delete mode 100644 docs-mini/README.MacOS delete mode 100644 docs-mini/README.Win32-X delete mode 100644 docs-mini/README.mingw delete mode 100644 docs-mini/README.plib diff --git a/docs-mini/README.Cygwin b/docs-mini/README.Cygwin deleted file mode 100644 index bf53fce7c..000000000 --- a/docs-mini/README.Cygwin +++ /dev/null @@ -1,25 +0,0 @@ -This is what [Norman Vine ] recommends for general -Cygwin development. - -Note: This will be a Unix like system and not a Windows IDE It is -expected that the user is comfortable using a unix development -environment, the gnu gcc compiler, and its asociated tools. -Alternatively if you don't mind typing commands from a command line -and reading instrunctions you should have a very good chance of -success. - -1) Latest Cygwin release - - Install the Cygwin toolkit by clicking on the "Install Cygwin Now" - link at http://www.cygwin.com - -2) Building from source - - Follow the instructions for building on Linux. - - - Your OpenGl libraries will be automatically installed - and you can ignore that section of the Linux readme. - -Any additional questions can be directed to Norman Vine -since he thinks this terse document is all you'll need. :-) diff --git a/docs-mini/README.IRIX b/docs-mini/README.IRIX deleted file mode 100644 index 9ca12e99d..000000000 --- a/docs-mini/README.IRIX +++ /dev/null @@ -1,73 +0,0 @@ - -This file is made possible by contributions from: - Todd Smith - Curt Olson - Erik Hofman - - -1. Requirements - -The following packages should be installed before FlightGear (or SimGear -or PLib) can be compiled on Irix: - - Irix development headers and libraries - (from the Irix 6.5 development CD's) - -------------------------------------- - - compiler_dev.sw.base irix_dev.sw.headers - compiler_dev.sw.ld dev.sw.lib - compiler_dev.sw.util - compiler_dev.hdr.lib - - gl_dev.sw.gldev dmedia_dev.sw.base - x_dev.sw.dev - - MipsPro C and C++ Compiler environment - --------------------------------------- - - c++_dev.hdr.lib c_dev.sw.c - c++_dev.sw.c++ c_fe.sw.c - c++_dev.sw.lib - c++_eoe.sw.lib - c++_fe.sw.c++ - - SGI Freeware packages - --------------------------------------- - - GLUT: http://freeware.sgi.com - ZLIB: http://freeware.sgi.com - - - FlightGear Flight Simulator Software - --------------------------------------- - - FlightGear: http://www.flightgear.org - SimGear: http://www.simgear.org - Plib: http://plib.sourceforge.net - - -2. Compiling and Installation - - -NOTE: Make sure automake version 1.8.1 or later is installed !!! - -To create a set of binaries it is important to follow these steps. This -will build a statically linked executable /opt/bin/fgfs - - 1. Install GLUT and Zlib - 2. Configure and install plib - 3. After extracting SimGear and FlightGear make sure to run autogen.sh first. - This will fix a linker problem for MipsPro compilers. - 4. Configure and install SimGear and then FlightGear - - -3. Running - -Before the FlightGear program could be run it is important to install the -FlightGear base package (the default is to extract the base package into -/opt/lib32). - -This package can be found at: http://www.flightgear.org - -When all is set and done, just run: /opt/bin/fgfs -To see the command line options, type: /opt/bin/fgfs -h diff --git a/docs-mini/README.MSVC b/docs-mini/README.MSVC deleted file mode 100644 index b4b7d748a..000000000 --- a/docs-mini/README.MSVC +++ /dev/null @@ -1,131 +0,0 @@ -Use FlightGear.sln to compile fgfs executable for Win32 or x64 architectures with Visual Studio 2008. -Previous versions of Visual Studio are not officially supported anymore. - -Precompiled librairies and headers for compiling Win32 executables with VS2008 : -ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-win32-VS90-3rdParty+OSG-20110801.zip - -Precompiled librairies and headers for compiling x64 executables with VS2008 : -ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-x64-VS90-3rdParty+OSG-20110801.zip - -These two archives only contain 'release' versions of librairies and executables. In addition, -the archives below contain 'debug' version of libraries and should be dezipped over the previous one. -ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-win32-VS90-3rdParty+OSG-20110801-debug.zip -ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-x64-VS90-3rdParty+OSG-20110801-debug.zip - -The VS2008 / v9.0 project files assume the directory layout below : - -Win32 build : - * any_directory_on_any_drive / - 3rdParty / ( includes plib, fltk, zlib, libpng, libjpeg, libtiff, freetype, libsvn, gdal, ... - bin / - include / - lib / - boost_1_44_0 / - boost / - lib / - source / ( Flightgear CVS directory - It can also be renamed FlightGear or anything else - src / - projects / - VC90 / - Win32 / ( generated at build time - Debug / ( Debug executable - Release / ( Release executable - FlightGear.sln ( Main solution - utils / - install / - msvc90 / - OpenSceneGraph / ( OSG CMake install - bin / - include / - lib / - SimGear / ( SimGear CVS directory - simgear / - projects / - VC90 / - -3rdParty, boost_1_44_0 and install/msvc90 are included in the Win32 3rdParty archive. - -x64 build : - * any_directory_on_any_drive / - 3rdParty.x64 / ( includes plib, fltk, zlib, libpng, libjpeg, libtiff, freetype, ... - bin / - include / - lib / - boost_1_44_0 / - boost / - lib64 / - source / ( Flightgear CVS directory - It can also be renamed FlightGear or anything else - src / - projects / - VC90 / - x64 / ( generated at build time - Debug / ( Debug executable - Release / ( Release executable - FlightGear.sln ( Main solution - utils / - install / - msvc90-64 / - OpenSceneGraph / ( OSG CMake install - bin / - include / - lib / - SimGear / ( SimGear CVS directory - simgear / - projects / - VC90 / - -3rdParty.x64, boost_1_44_0 and install/msvc90-64 are included in the x64 3rdParty archive. - -Typical setup should decompose into the following steps : - - 1. Install Visual Studio 2008 Express (http://msdn.microsoft.com/fr-fr/express/aa975050.aspx) - 2. Install msysGit (http://code.google.com/p/msysgit/) - 3. Create a new directory, say D:\FGFSDevel (or anything else) - 4. Unzip precompiled Win32 3rd party archive in it - 5. Open a Git Bash session and cd to the new directory ( cd /d/FGFSDevel ) - 6. Get SimGear sources from Gitorious : git clone git://gitorious.org/fg/simgear.git SimGear - 7. Get FlightGear source from Gitorious : git clone git://gitorious.org/fg/flightgear.git FlightGear - 8. Go to D:\FGFSDevel\FlightGear\projects\VC90 and double-click on FlightGear.sln - 9. Select the "Release" configuration - 10. Open file D:\FGFSDevel\SimGear\simgear\version.h.in and change @VERSION@ into "2.0.0" or any current version - 11. Save file as version.h in the same directory - 12. Start build (usually F7) - 13. Get the data from Gitorious too : git clone git://gitorious.org/fg/fgdata.git fgdata - 14. Wait... - 15. Add /install/msvc90/OpenSceneGraph/bin and /3rdParty/bin to your PATH environment variable - 16. Enjoy - programs are in D:\FGFSDevel\FlightGear\projects\VC90\Win32\Release - -It is also possible to compile a Debug version. This is only useful when hacking the code because -a Debug version is way slower than the Release one. - -The 64bit build is only available to people having the Professional edition of Visual Studio 2008. In that case, 15. above should be : - 15. Add /install/msvc90-64/OpenSceneGraph/bin and /3rdParty.x64/bin to your PATH environment variable - -When the manual build works, it is possible to start it from the command line. This is useful -when setting up a build server or automating the process of retrieving the code and building -it in a scheduled task. To do that : - - 1. open a command line window - 2. execute "C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat" - or "C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat" in a - 64bit environment (Vista 64-bit or Windows7 64-bit) - You should see : "Setting environment for using Microsoft Visual Studio 2008 x86 tools." - printed in the console - ( To start 64-bit build, the right environment is set with : - "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcvarsall.bat" amd64 - ) - 3. cd to the FlightGear project directory : - D: - cd \FGFSDevel\FlightGear\projects\VC90 (for example) - 4. start the build with the command line below : - msbuild FlightGear.sln /p:Configuration=Release /m - or - msbuild FlightGear.sln /p:Configuration=Debug /m - -That's all... - -Note: you may experience the error below running the msbuild command : -FlightGear\projects\VC90\FlightGear.sln : error MSB4018: The "ResolveVCProjectOutput" task failed unexpectedly. -...(lots of additionnal messages) - -In that case, remove the /m switch from the command line. diff --git a/docs-mini/README.MacOS b/docs-mini/README.MacOS deleted file mode 100644 index 250a10d54..000000000 --- a/docs-mini/README.MacOS +++ /dev/null @@ -1,33 +0,0 @@ -June 29, 2001 Update: - -This information is very old and incomplete. If you have interest in -building FlightGear for the Mac, I suggest you contact Darrell -Walisser for more information, or post to the -flightgear-devel@lists.sf.net mailing list. - - - -README.MacOS - -Jan 12, 1999. - -Here is a quick outline of *one* way you can build FG for MacOS: - - -1. Install Metrowerks CodeWarrior Pro 3 - - -2. Install the 'Mesa 3D Graphics Library' *** URL - - -3. Fetch the Flight Gear code. *** URL - - -4. Fetch the 'MWCWP3 Support' *** URL - - -5. Open 'MWCWP3 Support:Simulator:Simulator.mcp' and you are ready to compile. - - -6. I appreciate feedback. Tell me if this works for you ! If it doesn't, tell me - what went wrong. My email is *** who want do to the first-level support ? diff --git a/docs-mini/README.Win32-X b/docs-mini/README.Win32-X deleted file mode 100644 index 18ba4578f..000000000 --- a/docs-mini/README.Win32-X +++ /dev/null @@ -1,85 +0,0 @@ -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/docs-mini/README.mingw b/docs-mini/README.mingw deleted file mode 100644 index ff48a1a70..000000000 --- a/docs-mini/README.mingw +++ /dev/null @@ -1,109 +0,0 @@ -How to compile FlightGear with mingw -==================================== - - -MinGW & MSYS -============ - -You need to install mingw & msys: - -http://www.mingw.org - -You need at least: - -MinGW: binutils, gcc-core, gcc-g++, mingw-runtime, mingw-utils, w32api -I would recommed the gcc-3.4.4 versions. -MSYS: msys-1.0.10.exe, msys-autoconf, msys-automake, msys-libtool, msys-DTK. - -Please read instructions carefully. - -Set the follwing environment variables within msys shell. - -export CFLAGS="-I/usr/local/include -O2" -export CXXFLAGS="-I/usr/local/include -O2" -export CPPFLAGS=-I/usr/local/include -export LDFLAGS=-L/usr/local/lib - -Pthread-win32 -============= - -http://sources.redhat.com/pthreads-win32/ - -compile: -make GCE-inlined - -Install: -cp pthread.h sched.h semaphore.h /usr/local/include -cp linpthreadGCE2.a /usr/local/lib/libpthread.a -cp pthread-GCE.dll /usr/local/bin - -patch header: - ---- pthread.h Sat Oct 1 20:56:43 2005 -*************** -*** 210,218 **** - * ----------------- - */ - -! #if HAVE_CONFIG_H -! #include "config.h" -! #endif /* HAVE_CONFIG_H */ - - #ifndef NEED_FTIME - #include ---- 210,218 ---- - * ----------------- - */ - -! //#if HAVE_CONFIG_H -! //#include "config.h" -! //#endif /* HAVE_CONFIG_H */ - - #ifndef NEED_FTIME - #include - -OpenAL -====== - -Get OpenAL for instance from Creative - -OpenAL win32 package -install Redist - - -install: - -cd libs -reimp OpenAL32.lib -cp libopenal32.a /usr/local/lib -cd .. -mkdir /usr/local/include/AL -cp Include/* /usr/local/include/AL - - -zlib-1.2.3 -========== - -configure --prefix=/usr/local -make -make install - -plib-1.6.8 -========== -configure --prefix=/usr/local -make -make install - -simgear -======= -get simgear from CVS -configure --prefix=/usr/local -make -make install - -flightgear -========= -configure --prefix=/usr/local --with-threads -make -make install - diff --git a/docs-mini/README.plib b/docs-mini/README.plib deleted file mode 100644 index 8e4569d09..000000000 --- a/docs-mini/README.plib +++ /dev/null @@ -1,16 +0,0 @@ -[This file is mirrored in both the FlightGear and SimGear packages.] - -You *must* have plib version 1.6.0 or later installed on your system -to build FlightGear!" Flight Gear is no longer compatible with the -earlier versions of the library. - -You can get the latest version of plib from: - - http://plib.sourceforge.net - -Build notes: - -You should be able to just run "./configure" to configure the package -and use all of plib's defaults. Then run "make" followed by "make -install". By default, plib installs itself into /usr so if you don't -like this, be sure to specify an alternate prefix such as --prefix=/usr/local