789
edits
Keeping FlightGear (win32) up to date without compiling: Difference between revisions
Jump to navigation
Jump to search
Keeping FlightGear (win32) up to date without compiling (view source)
Revision as of 12:47, 6 July 2008
, 6 July 2008Removed a redundant (repeated) section.
(→Second step:: The CVS web interface no longer offers tarball downloads.) |
(Removed a redundant (repeated) section.) |
||
| Line 16: | Line 16: | ||
==Second step:== | ==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 changed. You have to download the newest data from the FlightGear data CVS repository using a CVS client. | 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 changed. You have to download the newest data from the FlightGear data CVS repository using a CVS client. | ||
Two CVS clients for Windows are | |||
* TortoiseCVS. See [[Using TortoiseCVS with FlightGear]]. | |||
* WinCVS. See below. | |||
This is a pretty big amount of bytes (about 1.5 GB!) so you should have a fast internet connection. | This is a pretty big amount of bytes (about 1.5 GB!) so you should have a fast internet connection. | ||
==Using WinCVS to hold the content of the [data] folder actual:== | ==Using WinCVS to hold the content of the [data] folder actual:== | ||
| Line 100: | Line 99: | ||
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 | ||
from the “Previous” field. | from the “Previous” field. | ||
==Last Words== | ==Last Words== | ||