FlightGear CVS: Difference between revisions

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


While new FlightGear features and additions are in development, they are available from CVS before they are available in the standard release version.  Using CVS allows a user to build the newest possible version of FlightGear from the latest source code, to experiment with new aircraft or other features.  However, it's not a beginner's tool.  Using CVS can expose the user to unstable features that show ugly error messages, or crash the computer.  Fortunately, very few of FlightGear's advanced features require CVS. (See [[New_to_FlightGear#Getting_Started|Getting Started]] for more info about using FlightGear without CVS).
While new FlightGear features and additions are in development, they are available from CVS before they are available in the standard release version.  Using CVS allows a user to build the newest possible version of FlightGear from the latest source files, to experiment with new aircraft or other features.  However, it's not a beginner's tool.  Using CVS can expose the user to unstable features that show ugly error messages, or crash the computer.  Fortunately, very few of FlightGear's advanced features require CVS. (See [[New_to_FlightGear#Getting_Started|Getting Started]] for more info about using FlightGear without CVS).


==FlightGear CVS Links==
==FlightGear CVS Links==
240

edits

Navigation menu