#393: Vertical speed indicator affected by sim speed up

[flightgear.git] / docs-mini / README.MSVC

diff --git a/docs-mini/README.MSVC b/docs-mini/README.MSVC
index dafc3c99f7b4fee05e411b0fe24e9f0a4974543b..b4b7d748a0b8346f04e9ed3ba8a51698afd587ef 100644 (file)
--- a/docs-mini/README.MSVC
+++ b/docs-mini/README.MSVC
@@ -1,11 +1,16 @@
 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-20100501.zip
+ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-x64-VS90-3rdParty+OSG-20110801.zip
 
-Precompiled librairies and headers for compiling Win32 executables with VS2008 :
-ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-win32-VS90-3rdParty+OSG-20100501.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 :
 
@@ -15,8 +20,9 @@ Win32 build :
          bin /
          include /
          lib /
-      boost_1_39_0 /
+      boost_1_44_0 /
          boost /
+         lib /
       source /                   ( Flightgear CVS directory - It can also be renamed FlightGear or anything else
          src /
          projects /
@@ -37,7 +43,7 @@ Win32 build :
          projects /
             VC90 /
 
-3rdParty, boost_1_39_0 and install/msvc90 are included in the Win32 3rdParty archive.
+3rdParty, boost_1_44_0 and install/msvc90 are included in the Win32 3rdParty archive.
 
 x64 build :
  * any_directory_on_any_drive /
@@ -45,8 +51,9 @@ x64 build :
          bin /
          include /
          lib /
-      boost_1_39_0 /
+      boost_1_44_0 /
          boost /
+         lib64 /
       source /                   ( Flightgear CVS directory - It can also be renamed FlightGear or anything else
          src /
          projects /
@@ -67,7 +74,7 @@ x64 build :
          projects /
             VC90 /
 
-3rdParty.x64, boost_1_39_0 and install/msvc90-64 are included in the x64 3rdParty archive.
+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 :
 
@@ -83,5 +90,42 @@ Typical setup should decompose into the following steps :
  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. Wait...
- 14. Enjoy - programs are in D:\FGFSDevel\FlightGear\projects\VC90\Win32\Release
+ 13. Get the data from Gitorious too : git clone git://gitorious.org/fg/fgdata.git fgdata
+ 14. Wait...
+ 15. Add <any_directory_on_any_drive>/install/msvc90/OpenSceneGraph/bin and <any_directory_on_any_drive>/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 <any_directory_on_any_drive>/install/msvc90-64/OpenSceneGraph/bin and <any_directory_on_any_drive>/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.