Re: [Flightgear-devel] How to compile Terragear-cs ?

2012-01-02 Thread Clément de l'Hamaide
Hi all, (1) Yes Geoff, as you said : this is a compromise. And I thinks the good compromise is to keep the same way as used in Brisa script. Many people are accustomed with Brisa script and I want my script is very similar to Brisa script in order to don't change accustomed of people. My scrip

Re: [Flightgear-devel] How to compile Terragear-cs ?

2012-01-01 Thread Jason Cox
How about this at the top of the script (in tried yet) $0 2>$1  |tee $logfile & Rediredt all script output and tee in background. Exit status should still stop the build and out put should be on screen as well as in the log file Sent from Samsung tabletGeoff McLane wrote:On Sun, 2012-01-0

Re: [Flightgear-devel] How to compile Terragear-cs ?

2012-01-01 Thread Jari Häkkinen
On 2012-01-01 20.17, Geoff McLane wrote: > But in doing this, as you point out, there is NO OUTPUT > to the console... > > Except as Jari pointed out, you can start the script > as a background process, and use a repeated tail > command to view the end of the LOG in a console... > > Or even start t

Re: [Flightgear-devel] How to compile Terragear-cs ?

2012-01-01 Thread Geoff McLane
On Sun, 2012-01-01 at 16:40 +0100, Clément de l'Hamaide wrote: > Hi Pete, Geoff, > > Now my script work perfectly. > Hi Clément, Glad to hear it is all now working fine... Sorry my explanation was not clear... 1. I assume, like Francesco's script, and mine, you have the command in the early

Re: [Flightgear-devel] How to compile Terragear-cs ?

2012-01-01 Thread Jari Häkkinen
On 2012-01-01 16.40, Clément de l'Hamaide wrote: > When I remove all " 2>&1 | tee -a $LOGFILE" and I replace it by a > simple ">> $LOGFILE" I see many less information in terminal when > script is running. It's very annoying to haven't information about > step in terminal... For example, when the

Re: [Flightgear-devel] How to compile Terragear-cs ?

2012-01-01 Thread Clément de l'Hamaide
Hi Pete, Geoff, Now my script work perfectly. When I remove all " 2>&1 | tee -a $LOGFILE" and I replace it by a simple " >> $LOGFILE" I see many less information in terminal when script is running. It's very annoying to haven't information about step in terminal... For example, when the script

Re: [Flightgear-devel] How to compile Terragear-cs ?

2011-12-31 Thread Geoff McLane
Hi Clément, Pete, This is a VERY GOOD effort. Thank you for sharing... Two things I see - (1) Use of ' 2>&1 | tee -a $LOGFILE' As expressed recently on the Atlas devel list, using this type of expression 'hides' the 'cmake', 'make' error exits... because the LAST action, prior to returning to

Re: [Flightgear-devel] How to compile Terragear-cs ?

2011-12-31 Thread Peter Sadrozinski
Never mind, Clément has figured it out, and his script is working. On Sat, Dec 31, 2011 at 9:41 AM, Peter Sadrozinski wrote: > As I have also run against this same compile problem in the past (and have > since forgotten how I got around it) I am offering a proposal to make > terragear slightly ea

Re: [Flightgear-devel] How to compile Terragear-cs ?

2011-12-31 Thread Peter Sadrozinski
As I have also run against this same compile problem in the past (and have since forgotten how I got around it) I am offering a proposal to make terragear slightly easier to compile: The terms of use of newmat are here: newmat11 terms of use As we already inc

[Flightgear-devel] How to compile Terragear-cs ?

2011-12-30 Thread Clément de l'Hamaide
Hi all, I would like to contribute to airports/sceneries. I'm young real pilot and I like to remake the airport where I fly in real life. I've seen that many people have many problem to compile TerraGear. This is why I started to create a similar "download_and_install" script than "brisa script