> I'm quite familiar with the concept of compling having a history of writing > programs and compiling in Fortran (Portran), Turbo Pascal and most recently > Visual Basic 6. > > In particular, I like Visual Studios IDE (Integrated Development > Environment) having used it for VB6. > > The missing link seems to be from CVS to C++ source code.
CVS is not a programming language; you don't convert CVS anything to C++ source code. CVS is a software application, used in a client-server fashion (i.e. there's a CVS server, and users interact with the CVS server by running their own CVS client programs . . .sorta like how you use a web browser (the client) to interact with webservers). What CVS is used for is to archive/store source code, and in particular keep track of all the changes that have been made to that source code. Developers use CVS to manage all the source code for a particular project: people can "check out" a copy of the source code, build executables from it, run it, make changes, build it, run it, make changes, etc., and when they're done, submit their changes back to the server. CVS makes managing the code and its versions/changes easy (well, easier, anyway); it also helps handle situations such as when two people are working on the same chunk of code at the same time, and want to submit changes to a file that don't necessarily mesh well. When people talk about building FlightGear from CVS, what that means is using a CVS client (for example, if you're on Windows, you can use WinCVS) to check out a copy of the FlightGear project from the FlightGear CVS server. Once you've done that, you have a source tree for FlightGear -- a bunch of directories/folders, subdirectories, etc., all full of the C++ source code files that FlightGear is built from. You can then proceed to build the FlightGear executable from that CVS version of the source code using whatever C++ compiler you have; the actual details of building FGFS depends upon OS/setup, and I'm not a Windows person so I'd have to stop here. -c _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
