Keeping FlightGear (win32) up to date without compiling: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(t)
m (Redirected page to FlightGear Git on Windows)
 
(11 intermediate revisions by 6 users not shown)
Line 1: Line 1:
There are three easy steps to keep up with the actual development of FlightGear:
#REDIRECT [[FlightGear Git on Windows]]
 
==First step:==
You can find the latest FlightGear development branch already compiled as a Windows(TM)
executable file (fgfs.exe) at
[ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32]
by Frederic Bouvier. There a lot of precompiled binaries, the newest one together with the latest FGRun. There are irregular updates, sometimes even nearly weekly.
 
So check the filename for the latest version.
fgfs-win32-20060710.zip tells you that it is the version of July 10, 2006. The download size will be
about then 5 MB.
 
This is an '''OSG''' (!!!) Version of''' FlightGear''' '''AND FGRun''', dated (compiled) '''2. Mai 2008'''
fgrun+fgfs-osg-win32-20080502.zip  6971 KB  02.05.2008  10:16:00
 
==Second step:==
It is obligatory to combine a new FlightGear binary mainprogram with the matching FlightGear data
not only to get the newest developments but as configuration files or dataformats might have got
changed.
You have to download the newest data from
[http://cvs.flightgear.org/cgi-bin/viewvc/viewvc.cgi/data/ http://cvs.flightgear.org/cgi-bin/viewvc/viewvc.cgi/data/]
 
At the bottom of the page you will find the link "Download tarball".
This is a pretty big amount of bytes (about 1 Gb!) so you should have a fast internet
connection.
You have to unzip the download before copying it into [YourFlightGearFolder].
 
==Using WinCVS to hold the content of the [data] folder actual:==
If you don't want to download all that stuff again and again it is more practical to download
information and data about what has changed since the last upgrade, this means using the CVS
system.
 
==Using WinCVS to hold the content of the [data] folder actual:==
 
Using WinCVS to hold the content of the [data] folder actual:
If you don't want to download all that stuff again and again it is more practical to download
information and data about what has changed since the last upgrade, this means using the CVS
system.
 
1. WinCVS download:
WinCVS is GNU General Public License (GPL).
http://www.wincvs.org/download.html
 
2. Unzip and read Install.txt. With the actual version of today you only have to run
“wincvs_setup.exe”,
the rest is done by the program, so don't keep attention to the other files.
 
3. When running WinCVS for the first time you are asked to install python on your system (in
case you don't have it already there). This all is very easy, just click on the link in the message
window and download a stable Windows binary version.
After downloading let Windows do all the installwork, just click on the downloaded file, 
ie “python-2.4.3.msi”.
In case the WinCVS window is still open, close the program and start it again after the python
installation has been finished.
 
4. Selecting or creating a download folder
It is highly recommended not to upgrade directly into your Flightgear data folder. If there are
any errors due to internet connection or otherwise you will not destroy you old FlightGear
data.
You may use WinCVS to create a new folder on one of your harddisks with enough space left
for the big download.
Use the yellow folder symbol (inside the red circle) to select or create your CVS folder. You
may name it as you like. WinCVS creates the data folder itself when downloading.
After selection, “your” CVS folder shows up, see the red dotted lines.
 
5. Now you are ready for downloading, you must have established your internet connection.
Only once you have to type in 2 command lines. But this has to be done very carefully
without any typo, otherwise you won't be successful.
 
6. Use “Admin” from the upper menuebar, then select “Command Line...”
 
7. The command line window shows up
 
8. Using the command line window:
a) the first time you have to type the commands into the little window.
This is always the same:
Use the [Enter] key, if your command line is too long and you have to write the rest into a
second line.
Use the [Control] + [Enter] keys if you are ready with you input.
Then press the “OK” button at the bottom of the window.
Start with:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login
Your password is “guest”.
Type “guest” (without quotation marks)
 
9. If all is ok, then you should read these messages:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 login
Logging in to :pserver:cvsguest@cvs.flightgear.org:2401:/var/cvs/FlightGear-0.9
<nowiki>***** CVS exited normally with code 0 *****</nowiki>
 
10. If the commandline window has disappeared, repeat step 6 of this manual
 
11. Your next commandline reads if it is the FIRST time you download CVS:
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data
The “Previous” field remembers your old commandline inputs:
 
12. Using WinCVS the SECOND time:
The login as described in (8) is much more fun as WinCVS remembers your commandline
inputs. Use the [arrow down] symbol of the “Previous” field and select the login command.
(see screenshot).
Then, as you already have a working CVS data folder the next commandline is very short:
cvs update -dP
 
13. You have to type this again into the commandline field.
Don't use the command as shown in (11) as this would write a complete new CVS!
If you start WinCVS the third time, you'll get all the necessary commands by selecting them
from the “Previous” field.
 
- [[Using TortoiseCVS with FlightGear]]
 
==Last Words==
Frederic Bouvier and Martin Spott are the provider of the Windows fgfs.exe and fgrun compilations
and server space. Frederic is also the author of fgrun. A big “thank you” to them for this service.
Keep up with the ongoing development of FlightGear. All the steps described above are very easy to
handle if you have read this document carefully.
Have much fun with FlightGear!

Latest revision as of 22:32, 16 June 2010