Do the instructions on http://linuxsimulations.org help even a bit?
Wrote it myself, let me know if it makes sense :). Tried to break the process down as much as possible. Matt On Sat, 2003-01-11 at 07:56, Mike Bonar wrote: > Please help a newbie out. I am a little confused about how to stay up to date > with CVS. Here's the process as documented, and as I understand it. > > cd /usr/local/source/FlightGear (the directory I created to hold FlightGear) > Connect to CVS server and checkout FlightGear > ./autogen.sh > ./configure > make > make install > Connect to CVS server and checkout fgfsbase > (Is there a step missing here? Do I need to copy the contents of fgfsbase to > /usr/local/lib/FlightGear?) > run fgfs > > Now, let's say a couple of days go by, and I want to get the latest CVS. > cd /usr/local/source/FlightGear (not /usr/local/lib/FlightGear?) > cvs update -d -P > here's where I get lost... > Do I run fgfs? > Do I rerun ./autogen.sh? > Do I rerun ./configure, make, and make install? > Does the update command give me FlightGear and fgfsbase, or do I need to cd to > /usr/local/fgfsbase, cvs update -d -P, and copy contents of fgfsbase to > /usr/local/lib/FlightGear? > > I guess I'm not really understanding the process. When I checkout FlightGear, > I get the source code. When I do the make install, does it create the > binaries and install them in /usr/local/lib/FlightGear? When I check out > fgfsbase, I get the data files, essentially. These do not require > compilation, correct? Do they need to be copied to /usr/local/lib/FlightGear > for the binaries to find them? Or is the --fg-root=/path/to/my/fgfsbase > parameter tell the binaries where the base files are? > > MIke _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
