Keeping FlightGear (win32) up to date without compiling: Difference between revisions
m (cleanups) |
|||
| Line 1: | Line 1: | ||
There are three easy steps to keep up with the | There are three easy steps to keep up with the latest developments in FlightGear: | ||
==First step:== | ==First step:== | ||
| Line 5: | Line 5: | ||
executable file (fgfs.exe) at | executable file (fgfs.exe) at | ||
[ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32] | [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32] | ||
by Frederic Bouvier. There | by Frederic Bouvier. There you will find several precompiled binaries, the most recent one also comes with the latest FGRun. While these are irregularly updated, they may sometimes be updated on a weekly basis. | ||
So check the filename for the latest version. | So check the filename for the latest version. | ||
| Line 15: | Line 15: | ||
==Second step:== | ==Second step:== | ||
It is obligatory to combine a new FlightGear binary | It is obligatory to combine a new FlightGear binary (the main program) with the matching FlightGear data (the base package) not only to get the newest developments but mostly because configuration files or data formats (fgfs internals) might have changed, so that an old fgfs core may not know how to deal with resources in a more recent version of the base package. | ||
You have to download the newest data from the FlightGear data CVS repository using a CVS client (as discussed [http://wiki.flightgear.org/index.phpKeeping_FlightGear_(win32)_up_to_date_without_compiling here]). | |||
Two CVS clients for Windows are | Two CVS clients for Windows are | ||
| Line 21: | Line 24: | ||
* WinCVS. See below. | * WinCVS. See below. | ||
The initial checkout from CVS is a pretty big amount of data (about 2 GB!) so you should have a fast internet connection and preferably a flatrate, too. | |||
==Using WinCVS to keep the base package updated:== | |||
If you don't want to download all that stuff again and again it is more practical to download | 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 | information and data about what has changed since the last upgrade, this means using the CVS | ||
| Line 35: | Line 36: | ||
http://www.wincvs.org/download.html | http://www.wincvs.org/download.html | ||
2. Unzip and read Install.txt. | 2. Unzip and read Install.txt. You only have to run “wincvs_setup.exe”, | ||
the rest is done by the program, so don't keep attention to the other files. | the rest is done by the program, so don't keep attention to the other files. | ||
| Line 42: | Line 42: | ||
case you don't have it already there). This all is very easy, just click on the link in the message | 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. | window and download a stable Windows binary version. | ||
After downloading let Windows do all the | After downloading let Windows do all the install work, just click on the downloaded file, | ||
ie “python-2.4.3.msi”. | ie “python-2.4.3.msi”. | ||
In case the WinCVS window is still open, close the program and start it again after the python | In case the WinCVS window is still open, close the program and start it again after the python | ||
installation has | installation has finished. | ||
4. Selecting or creating a download folder | 4. Selecting or creating a download folder | ||
It is highly recommended not to upgrade directly into your Flightgear data folder. | It is highly recommended not to upgrade directly into your Flightgear data folder. That way, if there are any errors due to internet connection or otherwise you will not corrupt/destroy your checkout of the FlightGear base package (you could however also keep a compressed image of the base package in a separate archive to be able to easily restore a CVS checkout). | ||
any errors due to internet connection or otherwise you will not destroy you | |||
You may use WinCVS to create a new folder on one of your harddisks with enough space left | You may use WinCVS to create a new folder on one of your harddisks with enough space left | ||
for the big download. | for the big download. | ||
| Line 58: | Line 57: | ||
5. Now you are ready for downloading, you must have established your internet connection. | 5. Now you are ready for downloading, you must have established your internet connection. | ||
When downloading for the first time, you have to type in 2 command lines. But this has to be done very carefully without any typo, otherwise you won't be able to checkout the base package. | |||
without any typo, otherwise you won't be | |||
6. Use “Admin” from the upper | 6. Use “Admin” from the upper menu bar, then select “Command Line...” | ||
7. The command line window shows up | 7. The command line window shows up | ||
| Line 70: | Line 68: | ||
Use the [Enter] key, if your command line is too long and you have to write the rest into a | Use the [Enter] key, if your command line is too long and you have to write the rest into a | ||
second line. | second line. | ||
Use the [Control] + [Enter] keys | Use the [Control] + [Enter] keys when you are ready (finished with your inputs). | ||
Then press the “OK” button at the bottom of the window. | Then press the “OK” button at the bottom of the window. | ||
Start with: | Start with: | ||
| Line 82: | Line 80: | ||
<nowiki>***** CVS exited normally with code 0 *****</nowiki> | <nowiki>***** CVS exited normally with code 0 *****</nowiki> | ||
10. If the | 10. If the command line window has disappeared, repeat step 6 of this manual | ||
11. Your next | 11. Your next command line reads if it is the FIRST time you download CVS: | ||
cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data | cvs -d :pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9 co data | ||
The “Previous” field remembers your old | The “Previous” field remembers your old command line inputs: | ||
12. Using WinCVS the SECOND time: | 12. Using WinCVS the SECOND time: | ||
The login as described in (8) is much more fun as WinCVS remembers your | The login as described in (8) is much more fun as WinCVS remembers your command line | ||
inputs. Use the [arrow down] symbol of the “Previous” field and select the login command. | inputs. Use the [arrow down] symbol of the “Previous” field and select the login command. | ||
(see screenshot). | (see screenshot). | ||
Then, as you already have a working CVS data folder the next | Then, as you already have a working CVS data folder the next command line is very short: | ||
cvs update -dP | cvs update -dP | ||
13. You have to type this again into the | 13. You have to type this again into the command line field. | ||
Don't use the command as shown in (11) as this would write a complete new CVS! | 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 | If you start WinCVS the third time, you'll get all the necessary commands by selecting them | ||
| Line 101: | Line 99: | ||
==Last Words== | ==Last Words== | ||
Frederic Bouvier and Martin Spott are the | Frederic Bouvier and Martin Spott are the providers of the Windows fgfs.exe and fgrun compilations (CVS snapshots) and server space. Frederic is also the author of fgrun. A big “thank you” to them for this service. | ||
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 | 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. | handle if you have read this document carefully. | ||
Revision as of 14:18, 4 October 2008
There are three easy steps to keep up with the latest developments in FlightGear:
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
by Frederic Bouvier. There you will find several precompiled binaries, the most recent one also comes with the latest FGRun. While these are irregularly updated, they may sometimes be updated on a weekly basis.
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 5 MB.
This is an OSG (!!!) Version of FlightGear AND FGRun (compiled), dated 21st of June 2008. Search for this, the latest version at time of editing. It will depend on what browser you are using too: fgrun+fgfs-osg-win32-20080621.zip 6992 KB 21/06/2008 17:36:00
Second step:
It is obligatory to combine a new FlightGear binary (the main program) with the matching FlightGear data (the base package) not only to get the newest developments but mostly because configuration files or data formats (fgfs internals) might have changed, so that an old fgfs core may not know how to deal with resources in a more recent version of the base package.
You have to download the newest data from the FlightGear data CVS repository using a CVS client (as discussed here).
Two CVS clients for Windows are
- TortoiseCVS. See Using TortoiseCVS with FlightGear.
- WinCVS. See below.
The initial checkout from CVS is a pretty big amount of data (about 2 GB!) so you should have a fast internet connection and preferably a flatrate, too.
Using WinCVS to keep the base package updated:
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. 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 install work, 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 finished.
4. Selecting or creating a download folder It is highly recommended not to upgrade directly into your Flightgear data folder. That way, if there are any errors due to internet connection or otherwise you will not corrupt/destroy your checkout of the FlightGear base package (you could however also keep a compressed image of the base package in a separate archive to be able to easily restore a CVS checkout).
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. When downloading for the first time, you have to type in 2 command lines. But this has to be done very carefully without any typo, otherwise you won't be able to checkout the base package.
6. Use “Admin” from the upper menu bar, 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 when you are ready (finished with your inputs). 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 ***** CVS exited normally with code 0 *****
10. If the command line window has disappeared, repeat step 6 of this manual
11. Your next command line 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 command line inputs:
12. Using WinCVS the SECOND time: The login as described in (8) is much more fun as WinCVS remembers your command line 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 command line is very short:
cvs update -dP
13. You have to type this again into the command line 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.
Last Words
Frederic Bouvier and Martin Spott are the providers of the Windows fgfs.exe and fgrun compilations (CVS snapshots) 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!
| |||||||||||
If you are lost see Portal:User or Portal:Developer