X-Git-Url: https://git.mxchange.org/?a=blobdiff_plain;f=docs-mini%2FREADME.MSVC;h=b4b7d748a0b8346f04e9ed3ba8a51698afd587ef;hb=4d4e1a237165768e9abcf98a4251a9cefacb5093;hp=17e79095ccca2c74fb56280524487e676e9b75a1;hpb=0bce31ae9a80c571b9126427c093b8dc3d3f6820;p=flightgear.git

diff --git a/docs-mini/README.MSVC b/docs-mini/README.MSVC
index 17e79095c..b4b7d748a 100644
--- 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 :
 
@@ -91,8 +98,8 @@ Typical setup should decompose into the following steps :
 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, 14. above should be :
- 14. 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
+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 
@@ -104,6 +111,9 @@ it in a scheduled task. To do that :
      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)
@@ -113,3 +123,9 @@ it in a scheduled task. To do that :
      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.