FlightGear CVS: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
m (minor copy edit)
(copy edit)
Line 1: Line 1:
Many FlightGear developers use '''CVS''', a '''Concurrent Versions System''' to store all of the files required to compile and build FlightGear.  CVS keeps track of every update as developers around the world work together, concurrently, to create new versions of the files.
==Introduction==
Many [[FlightGear]] developers use '''CVS''', a '''Concurrent Versions System''' to store all of the files required to compile and build FlightGear.  CVS keeps track of every update as developers around the world work together, concurrently, to create new versions of the files.


This means the newest features, fixes, and additions to FlightGear, which are still in development, are available in CVS before they are available in the stable release.  CVS is a tool for users who want to build the newest possible version of FlightGear from source code, or experiment with new aircraft or other features which are not yet available in the stable release version.
This means the newest features, fixes, and additions to FlightGear, which are still in development, are available in CVS before they are available in the stable release.  CVS is a tool for users who want to build the newest possible version of FlightGear from source code, or experiment with new aircraft or other features which are not yet available in the stable release version.


However, CVS is a tool for advanced users and developers.  Using CVS can expose the user to unstable features which spew ugly error messages or crash the computer.  Fortunately, CVS is not required, even for advanced users, to use the stable release versions of FlightGear.  See [[New_to_FlightGear#Getting_Started|Getting Started]] for info on using FlightGear without CVS.
However, CVS is a tool for advanced users and developers.  Using CVS can expose the user to unstable features which spew ugly error messages or crash the computer.  To prevent bugs and errors, CVS aircraft may require the user to compile the matching CVS version of FlightGear.  Fortunately, CVS is not required, even for advanced users, to use the stable release versions of FlightGear.  See [[New_to_FlightGear#Getting_Started|Getting Started]] for info on using FlightGear without CVS.


==FlightGear and CVS==
==FlightGear CVS Links==
[[FlightGear]]'s CVS is available [http://cvs.flightgear.org/viewvc/ here] and can be considered as the most up-to-date version of the FlightGear source and [[aircraft]]. To run CVS aircraft the user need to use the CVS, to prevent bugs and faults. The [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-cvslogs CVS Changelog] shows all updates made to the CVS repository.
*The FlightGear CVS repository is available at [http://cvs.flightgear.org/viewvc FlightGear CVS]
*The [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-cvslogs CVS Changelog] shows all updates made to the CVS repository.


==How to use FlightGear's CVS==
==How to Use FlightGear CVS==
Windows: Easy! The following instructions will lead you to your goal. They are very similar, you will probably not have to read all of them:
 
====Windows====
* [[Flightgear 1.0 to CVS : Piece of Cake]]
* [[Flightgear 1.0 to CVS : Piece of Cake]]
* [[Using TortoiseCVS with FlightGear]]
* [[Using TortoiseCVS with FlightGear]]
* [[Keeping FlightGear (win32) up to date without compiling]]
* [[Keeping FlightGear (win32) up to date without compiling]]


Linux: Easy.
====Linux====
* (Ubuntu/Debian): Just use the download_and_compile.sh script, instructions here:[[Scripted_Compilation_on_Linux_Debian/Ubuntu]]
* (Ubuntu/Debian): Just use the download_and_compile.sh script, instructions here:[[Scripted_Compilation_on_Linux_Debian/Ubuntu]]
* Manual step by step instructions: http://wiki.flightgear.org/index.php/Building_FlightGear_-_Linux
* Manual step by step instructions: http://wiki.flightgear.org/index.php/Building_FlightGear_-_Linux


Mac: Slightly trickier:
====Mac====
* [http://macflightgear.sourceforge.net/home/documents/how-to-build-flightgear-cvs-on-mac-os-x/ How to build FlightGear cvs on Mac OS X]
* [http://macflightgear.sourceforge.net/home/documents/how-to-build-flightgear-cvs-on-mac-os-x/ How to build FlightGear cvs on Mac OS X]


If you want to get really into it, see also:
====See Also====
* [http://www.flightgear.org/cvs/anoncvs.html Instructions for the FlightGear CVS repository]
* [http://www.flightgear.org/cvs/anoncvs.html Instructions for the FlightGear CVS repository]


Revision as of 17:06, 11 December 2009

Introduction

Many FlightGear developers use CVS, a Concurrent Versions System to store all of the files required to compile and build FlightGear. CVS keeps track of every update as developers around the world work together, concurrently, to create new versions of the files.

This means the newest features, fixes, and additions to FlightGear, which are still in development, are available in CVS before they are available in the stable release. CVS is a tool for users who want to build the newest possible version of FlightGear from source code, or experiment with new aircraft or other features which are not yet available in the stable release version.

However, CVS is a tool for advanced users and developers. Using CVS can expose the user to unstable features which spew ugly error messages or crash the computer. To prevent bugs and errors, CVS aircraft may require the user to compile the matching CVS version of FlightGear. Fortunately, CVS is not required, even for advanced users, to use the stable release versions of FlightGear. See Getting Started for info on using FlightGear without CVS.

FlightGear CVS Links

How to Use FlightGear CVS

Windows

Linux

Mac

See Also

Building/Compiling
FlightGear
TerraGear
Related
Retrieved from "https://wiki.flightgear.org/w/index.php?title=FlightGear_CVS&oldid=18446"