<snip>
Any date or version will serve.
Here's how to do it:
1. Create a new work directory for fg builds you are going to use the
next/experimental version on. Mine is ~/work/fg
2. In the new work directory, place a copy of the experimental
download_and_compile.sh
3. Create directories for the versions of fgdata you are going to need:
~/work/fg/fgdata_2.11.0
~/work/fg/fgdata_2.10.0
~/work/fg/fgdata_2.8.0
Depending on how much you like to test, you can create just one
of these and copy -R your downloaded copy into it. Or you can
copy -R into all three. The script should be able to handle it
either way. Also, it should not matter which version you put in
these directories. The script should be able to reset them to
the right version when a build is done for that version.
So far, everything is in your new work directory. Builds
happen one level down.
4. Create a directory for the build you want to do
~/work/fg/master
~/work/fg/next
~/work/fg/stable
~/work/fg/2.10.0
~/work/fg/2.8.0
5. cd to the directory you want to build and do the right build
for example:
cd ~/work/fg/next
../download_and_compile.sh -p n -d y -xv all
cd !/work/fg/2.10.0
../download_and_compile.sh -p n -d y -xv j 3 -B 2.10.0 -R HEAD all
Now if you have to blow away one of your build directories, fgdata stays
put, safe and sound in the top of your fg work tree.
I'm taking bets on how long it takes you to find a bug... Happy
hunting.
-Pat
> ..to avoid the 3-day delay fetching a new 5GB copy of fgdata,
> where do I put my "March 29'th-current" copy of fgdata?
> I now have it as 2.11.0 in ~/FG-git/fgdata
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
