Re: [Flightgear-devel] Scripted Installation - An update and a summary of where things stand.

2013-09-01 Thread Pat
I'm going to try to limit the versions to one focused change set from
now on.  That may make the changes smaller and easier to understand
and test.

updated team master 1.9.12 (bugfix and preliminary logging changes
useful for debugging 1.9.12) 

team next now contains a version 1.9.13 (main logging changes)

Version 1.9.13 address the -x and -v log output not appearing in the log
file

Version 1.9.14 will address directory management. (fgsrc, othersrc and
using directory variable names instead of cd .. and cd - )

-Pat

download_and_compile.sh 1.9.13-pre1

1. download_and_compile.sh log file's name is changed to
   download_and_compile.log

2. Previously the log file contained only data specifically
   directed to $LOGFILE.  1.9.13 directs all output to
   download_and_compile.log.  Visually distracting constructs
   like  2>&1 | tee -a $LOGFILE are no longer found throughout
   the script.
3. When -x and/or -v is used, the output of -x and -v is
   visible in the log file.

4. download_and_compile_summary.log, added in 1.9.12,
   now contains a list of the start and finish times
   for each build step

5. Miscellaneous historical comments have been removed

6. write_log(), introduced in 1.9.12 is used more.
   write_log puts output in download_and_compile.log and
   in download_and_compile_summary.log

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


[Flightgear-devel] Scripted Installation - An update and a summary of where things stand.

2013-08-31 Thread Pat
Lets review where things stand with the script:



Current commit on team clone:
 download_and_compile.shAug 31 2013 #58ae270 Version
 1.9.12 (Pat)

http://www.gitorious.org/fg/fg-download-and-compile-fgmeta/raw/58ae27079531e69ec48c6df06538559680bd9433:download_and_compile.sh

Contains a fix to a bug found and reported by Arnt.

Additional testing is needed before this can be merged to the main
fgmeta.

A detailed list of the changes in the script version
1.9.12 can be found here:

http://www.gitorious.org/fg/fg-download-and-compile-fgmeta/commit/58ae27079531e69ec48c6df06538559680bd9433
Francesco approved an early version of 1.9.12. There have been
additional small changes made.  

-Pat




For Arnt and others interested in where things are going, the following
summarizes a lot of stuff that's already been said here and elsewhere.

The current "official" script in fgmeta is 1.9.11 
It builds 2.8.0 as stable and will build next. It would need small
modifications to build 1.9.10 or 1.9.12 

Arnt has requested details on any new design for the directory
structure.  I've given one below, but I'm open to suggestions if you'd
prefer something different.

Here are the design goals:

1.  download_and_compile.sh continues to work exactly as it has in the
past.  It will continue to use the same directory structure unless
the user decides to take an action that causes a new directory
structure to be adopted for subsequent builds.

2.  Minimize the impact on git and svn servers by removing the need to
download multiple copies of sources and data.

3.  Facilitate testing the script with different versions and options.

To meet these goals there are several features being added to the
script.  Some of these are partially in place, some will require
additional changes.

Changes through script version 1.9.12:
=== === == === ===

1. Terminal Window Titles

2. Additional versions of OSG supported

3. Support for any branch, including the soon to be released flightgear
   2.12.0.  2.10.0 is considered stable at this point in time.

4. Use manually placed fgdata copies in the parent of the build
   directory.  

   Copies of fgdata git repositories can be placed in directories
   named fgdata_2.8.0, fgdata_2.10.0, fgdata_2.12.0 and fgdata_2.99.9. 
   
   If download_and_compile.sh is run from a sub-directory of the 
   directory containing the fgdata* directories, instead of downloading 
   a separate copy of fgdata, the script will simply create s symbolic
   link to the correct fgdata git copy.  

   Note that initially all the copies' versions do not have to match
   the directory name.  Any recent version of fgdata will do.  When it
   runs, the script will update the version you are building to be the
   correct version of fgdata.

   This approach to keeping multiple fgdata versions 
   means you never have to download fgdata more than once.  

1. You can blow away a build and not have to redownload fgdata
2. You can have multiple variant builds of a single version all
   using the same fgdata_*/fgdata version
3. You can build different versions of flightgear and still not
   have to download another fgdata

== 
Future Changes:
== 


1. Change the directory structure for sources to allow a single copy of
   the sources to be used for multiple versions and variants without
   having to download the sources repeatedly.

   Similarly to the placement of the fgdata_* copies, create new
   directories for sources: 

fgsrc
which will contain sources for anything native to
flightgear
othersrc 
which will contain sources for plib and as many
versions of OSG as you need.

Builds will be done in a subdirectory, one per variant

It will look something like:

download_and_compile.sh

fgdata_2.10.0
fgdata
fgdata 2.12.0
fgdata
fgdata 2.99.9
fgdata
fgsrc
flightgear
simgear
openrti
fgcom (unless we abandon the separate fgcom)
fgrun
etc.
othersrc
OpenSceneGraph-3.0.1
OpenSceneGraph-3.1.9

plib-1.8.5

variant-2.12.0-openrti
build
install
compilation_log.txt

variant-2.10.0-noopenrti
build
install
compilation_log.txt

variant-master-openrti
variant-master-noopenrti
variant-next-noopenrti
variant-next-noopenrti
and so forth.


Note that with 1.9.12 and later its possible to build the
master branch.

Usage:

cd variant-master-openrti
../download_and_compile.sh [options] [component names]

2. Change the wa