[Flightgear-devel] New alpha version of download_and_compile.sh - avoids multiple fgdata downloads.

[Pat <pat...@gm...>]

I've put a new version of download_and_compile.sh on the team clone 

http://www.gitorious.org/+fg-download-and-compile/fg/fg-download-and-compile-fgmeta/blobs/next/download_and_compile.sh

The big change:

	This version changes the way fgdata is handled to prevent
	multiple downloads of the 5G of git archives for fgdata.
	Multiple versions of fgdata can be kept active and up to date
	for testing purposes.  Various build and install trees can be
	created using download_and_compile.sh. Each of these will use
	symlinks to the appropriate fgdata version.

This is an alpha version 

	It has not been approved for the main tree.

	It has had some testing, but needs others to try it out to
	uncover any bugs.  I recommend using it in a separate directory
	from your usual builds until you have some confidence in how it
	works.  

If you find a bug, create a detailed log by running it like this:

 	./download_and_compile.sh -xv >download_and_compile_diagnostics.log

	This log is likely to be large.  Please don't e-mail it to the
	list.

	Instead, Email me, find me on irc #flightgear as user pac1 or
	contact me through the flightgear forum.  If you've got my
	phone #, feel free to use it.

Here's the commit note for the change:

Add -D option to change the handling of fgdata

	With this change a download_and_compile.sh user can optionally
	use a single copy of fgdata as a base for builds using any
	other version.

	The -D option will find and create if not found, version
	directories for fgdata.  Once this is done for one version,
	download_and_compile.sh will use these directories to prevent
	multiple downloads of the entire 5gb git archive, when a
	different version of fgdata is needed.  The directories are
	initially placed at the same level as download_and_compile.sh.
	The directories can be moved higher in the directory tree if
	desired.

	When an existing or new build and install tree needs to use a
	particular version of fgdata, a symlink in fgfs/install will
	connect the build to the correct version.  If the correct
	version does not yet exist it will be copied from an existing
	fgdata of another version and changed to the needed version
	using git checkout.

	This allows download_and_compile.sh to create as many build and
	install trees as desired, each with different versions and
	options, while keeping network usage to a minimum.

	a typical set of fgdata and separate build directories  might
	look like:

	~/work/fg
	~/work/fg/fgdata_2.8.0
	~/work/fg/fgdata_2.10.0
	~/work/fg/fgdata_2.11.0
	~/work/fg/master
	~/work/fg/master-openrti-debug
	~/work/fg/stable
	~/work/fg/2.10.0-debug

	for each build, the required symlink will be created to the
	corresponding fgdata_* directory.