The next branch on the team clone has the changes to download and
compile.sh listed below. There are just a couple of things left to do,
plus extensive testing.
I gave up on trying to do small incremental changes to the script.
There would be too many variations to test if what I wanted to
accomplish were done in small steps.
its all available here:
Initial testing is complete
Variant builds work well and flightgear/fgcom/fgrun all start
and run as expected.
I've used it with -G 3.1.9 and it built. It remains
to be proven that it actually built using OSG-3.1.9 or 3.0.1 as usual..
Try your favorite combinations of parameters and let me know how things
work for you.
Remember this is an alpha version. Not yet approved for general use.
put download_and_compile.sh in a new directory, away from
your current build
create a subdirectory and run ../download_and_compile.sh
Recently added options:
-G OSG version number
-B Version # for Flightgear and Simgear, should
correctly resolve version for openrti
-R sets a revision for Flightgear and Simgear
-D 1 Directory management option (reduces disk space, clutter,
and network usage
-N x -DSG_SVN_CLIENT=$OPTARG
-g may actually work
-w verbose makefile
-x sets -x
-v sets -v
Here's what I have been working on. The next branch has most of this
0. Change the title of the window in which the build is run
Indicate what variant is being worked on and which component
is currently being built.
1. Timestamped log files with or without -x, -v or -xv
2. Build any of next, master, 2.10.0, 2.8.0
2a. Build with any git tag.
2b. If building only one part, such as flightgear, simgear or
openrti, you can specify a commit #.
3. Build the old way and get the same simple directory
Variant builds are done as usual in separate directories which
contain the entire flightgear component trees including fgdata.
4. a rebuild script is left in the build directory.
Executing it will rerun Download_and_compile.sh with the same
options. The script documents what was built and the final
status of the most recent build.
5. Support for personal and team clones on gitorious.
6. Build a new way and get a directory structure:
Variant builds are still done in separate directories,
but contain only the variant's build and install directories
A parent directory, above the variant build directories
fgsrc: sources for flightgear, openrti, simgear, fgrun,
fgcom, fgcomgui etc
othersrc: sources for OSG (mulitple versions
supported), sources for plib (version 1.8.5 supported)
containers for different versions of fgdata:
fgdata_2.12.0, fgdata_2.11.0, fgdata_2.10.0, fgdata_2.8.0 etc.
This new directory structure supports:
1. No more multiple downloads of fgdata for each
separate build. You download only one, and if you need
more than one version, it is created locally with copy
and git commands. All variant builds use a copy of
fgdata from a parent directory
2. No more multiple download and builds of plib and
osg. You download and build plib-1.8.5 and osg-3.0.1
3. A single copy of flightgear, simgear and openrti
sources that can be used to build whatever versions are
4. Support for additional versions of osg such as 3.1.9