I did actually speak with Brisa this afternoon, and he will probably merge the
changes tomorrow or in the next few days. I only posted this version to the ML
because the changes to FGCOM compilation are a couple of weeks old and I
thought Francesco had already requested them to be included into GIT. I have my
own slightly divergent copy of the script, and only realized the issue was
still outstanding when someone on IRC was having trouble compiling a couple of
days ago.
Ciao,
Alessandro
> Date: Wed, 18 May 2011 20:52:01 +0200
> From: bre...@gmail.com
> To: flightgear-devel@lists.sourceforge.net
> Subject: Re: [Flightgear-devel] Modified download_and_compile.sh script
>
> On 18.05.2011 01:08, TDO_Brandano - wrote:
> > I have applied a couple of small modifications to the script to fix
> > FGCOM and ATLAS compilation with the current repository versions of
> > both. The changes are relatively small, just a couple of sed rule
> > changes for the FGCOM makefile and a renamed function in ATLAS to match
> > the updated SimGear. I have also altered the script version string and
> > name to avoid confusion with Brisa's original, but I have no idea on who
> > decides what is the current version of the script. Could someone have a
> > quick look at the attached copy and see if the changes can be ported
> > over to GIT?
>
> Hi Brandano,
> I placed the script in GIT since
> a) we want all build scripts to be part of the new "fgmeta" GIT
> repository, which at some point will also reference consistent
> simgear/flightgear/fgdata sets (and keep the history of matching
> revisions) - so anyone can just pull "fgmeta" and always get a
> consistent snap shot - including the build scripts.
> b) we needed a repository where we can change all required versions
> (flightgear, osg, ...) used by the build script whenever there's a need
> to change. And we needed to stop it from using osg-trunk by default.
>
> What I didn't intend was to fork the script - so changing the name would
> go in the wrong direction. It'd be great if you could try to contact
> Brisa first and ask him to review or merge the scripts - so we avoid
> maintaining separate branches here.
> I'm happy to add any updates/improvements to fgmeta. You or Brisa could
> send updates to me (or even place a GIT merge request). But I'd prefer
> if Brisa stayed in the loop.
>
> cheers,
> Thorsten
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
