* [EMAIL PROTECTED] (Matthew Law) [2002.09.19 17:47]:
> After many newbie-fied mistakes and misunderstanding I have now setup 
> /home/cvsroot on my linux box and checked out up-to-date copies of the devel 
> releases into:
> 
> /home/cvsroot/SimGear
> /home/cvsroot/FlightGear
> /home/cvsroot/fgfsbase
> 
> I also have a stable and working FGFS 0.8 which I'd like to keep (to play with 
> if I bugger up the CVS version!).  How do you guys compile a development 
> version beside a stable one without it interfering? In other words what do 
> you specify to ./configure when compiling these sources to keep them from 
> starting a fist fight with each other?

I don't think anyone replied to you main question, so I'll share with
you how I have everything setup.  First of all, I never alter my real
CVS directories -- I work on copies of them.  For example, here's my FG
paths:

/archive/incoming/flightgear/cvs/fgfs/Makefile
/archive/incoming/flightgear/cvs/fgfs/FlightGear/
/archive/incoming/flightgear/cvs/fgfs/local/
/archive/incoming/flightgear/cvs/fgfs/localbuild/

My Makefile looks like this:

all:
        rm -rf ./local ./localbuild
        cp -a ./FlightGear local
        mkdir localbuild
        lndir -silent ../local ./localbuild

So, what I do is cd to /archive/incoming/flightgear/cvs/fgfs/FlightGear
and update my local CVS checkout.  Then go back a directory and run
`make` to get a clean development copy.  I do all my local work in the
localbuild/ directory.  If I make changes, I cd back into the real CVS
directory and do a diff like so:

  $ diff -urN . ../local

I make no promises about this setup -- no warranty whatsoever.  :-)  I
only do small updates and bugfixes so I never really need to keep a
development tree around for a long time.  You'll have to talk to some of
the other "real" developers if you want to do that.  :-)
-- 
Cameron Moore
/ One cannot guess the real difficulties \
\  of a problem before having solved it. /

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to