Re: [Flightgear-devel] GIT : Nasal runtime error: No such member: asin

[grtuxhangar team]

Hello Anders,

Thanks for the quick reply, yes we had some sync issue with our Git.
right now  that's OK

Kind regards,

Ahmad


On 14 October 2013 14:15, Anders Gidenstam  wrote:

> On Mon, 14 Oct 2013, grtuxhangar team wrote:
>
>  Hello,
>>
>> with FG 2.99 Data  i am getting
>>
>> Nasal runtime error: No such member: asin
>>   at /devel/fgdata_git/Nasal/geo.**nas, line 173
>>   called from: /devel/fgdata_git/Nasal/view.**nas, line 306
>> called from: /devel/fgdata_git/Nasal/view.**nas, line 265
>> called from: /devel/fgdata_git/Nasal/view.**nas, line 217
>> called from: /devel/fgdata_git/Nasal/view.**nas, line 719
>>
>
> Please verify that your SimGear build is up to date. The math.asin
> function was moved to C++ code over a week ago and I have seen no other
> breakage reports and as far as I've noticed my own FG build works.
>
>
> Cheers,
>
> Anders
> --
> --**--**
> ---
> Anders Gidenstam
> WWW: http://gitorious.org/anders-**hangar
>  
> http://www.gidenstam.org/**FlightGear/
>
> --
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] download_and_compile.sh - version 1.9.12 finally ready

[Pat]

Geoff,

Thanks for testing this.  

I left a set -x on line 371 which causes the double output you're
seeing on -h. I've removed it.
 
Also, I've changes the svn
for plib to http://svn.code.sf.net/p/plib/code/trunk/.

OSG and PLIB are slated for different treatment in a future version.

If the chosen version of OSG, or the 1.8.5 version of PLIB is
installed or previously built, there's no reason to reconfigure
or rebuild them.

In general, I'd like to be able to detect when git does not add a file
to the sources.  Then I could condition the configure step on whether
its actually needed or not.  If I find a way to do that quickly, it
could be applied to any component that uses git, not just OSG.

I'll be using your approach for plib at least.

The latest is still 1.9.12:

https://www.gitorious.org/fg/fg-download-and-compile-fgmeta/raw/master:download_and_compile.sh

-Pat

On Thu,
10 Oct 2013 12:50:15 +0200 Geoff McLane  wrote:

> Hi Pat,
> 
> Finally got a chance to try download_and_compile.sh 
> 1.9.12 from the ...-fgmeta repo...
> 
> I think you need to adjust the svn repo for plib! It 
> has permanently changed I think
> 
> About ln 649
>   svn $PLIB_STABLE_REVISION_ co
> http://plib.svn.sourceforge.net/svnroot/plib/trunk/ plib 
> to the new repo
>   svn $PLIB_STABLE_REVISION_ co
> http://svn.code.sf.net/p/plib/code/trunk plib 
> 
> Also, as a suggestion, why not first search the system for an 
> installed plib, and use that rather than a new download 
> and compile? These days I have add plib as a 'system'
> install...
> 
> In my makefg, which as you know was based on one of 
> Brisa's original versions, circa Jan 2009, I use 
> script like -
> 
> # if NO plib installed path from user, and none from
> # previous configuration file, then
> if [ -z "$INSTALL_DIR_PLIB" ]; then
> # try the 'system' places
> PLIB_PATH="/usr"
> if [ -f "$PLIB_PATH/include/plib/ul.h" ]; then
> show_plib_version $PLIB_PATH
> PLIB_INSTALL_OK=1
> elif [ -f "$PLIB_PATH/local/include/plib/ul.h" ]; then
> show_plib_version "$PLIB_PATH/local"
> PLIB_INSTALL_OK=1
> else
> PLIB_PATH=""
> fi
> fi
> 
> The function 'show_plib_version' just reads the version
> from the ul.h header...
> 
> Anyway, just a suggestion...
> 
> After the above svn correction, the script ran to 
> the end, building fgcom, fgfs, fgrun, openrti,
> OpenSceneGraph, plib, simgear... great stuff...
> 
> I only had a chance to try it with the ALL option ;=))
> 
> But found out later that is not really 'ALL'. I could 
> add FGX, FGO?, FGCOMGUI, ATLAS and DATA, but I have 
> already done the DATA separately overnight... 
> 
> I will try to get around to trying the others... 
> presently doing -p FGX, but it insists on rebuilding 
> OSG which is slow...
> 
> One little thing. When I say run it with the -h help 
> option for example my bash shell echos the echo 
> lines, like the script has say -
>echo "Switches:"
> 


--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] The castAR Kickstarter is now live.

[geneb]

http://www.kickstarter.com/projects/technicalillusions/castar-the-most-versatile-ar-and-vr-system

The castAR stands to do a LOT to improve the visuals for both DIY and 
commercial flight simulators.  Because it's "AR" and not "VR", it can also 
be used to generate in-cockpit displays by covering the display area of 
something like a PFD with the retro-reflective material it uses.

Check it out.

g.

-- 
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.diy-cockpits.org/coll - Go Collimated or Go Home.
Some people collect things for a hobby.  Geeks collect hobbies.

ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://scarlet.deltasoft.com - Get it _today_!

--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] GIT : Nasal runtime error: No such member: asin

[Anders Gidenstam]

On Mon, 14 Oct 2013, grtuxhangar team wrote:


Hello,

with FG 2.99 Data  i am getting

Nasal runtime error: No such member: asin
  at /devel/fgdata_git/Nasal/geo.nas, line 173
  called from: /devel/fgdata_git/Nasal/view.nas, line 306
called from: /devel/fgdata_git/Nasal/view.nas, line 265
called from: /devel/fgdata_git/Nasal/view.nas, line 217
called from: /devel/fgdata_git/Nasal/view.nas, line 719


Please verify that your SimGear build is up to date. The math.asin 
function was moved to C++ code over a week ago and I have seen no 
other breakage reports and as far as I've noticed my own FG build works.



Cheers,

Anders
--
---
Anders Gidenstam
WWW: http://gitorious.org/anders-hangar
 http://www.gidenstam.org/FlightGear/--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] GIT : Nasal runtime error: No such member: asin

[grtuxhangar team]

Hello,

with FG 2.99 Data  i am getting

Nasal runtime error: No such member: asin
  at /devel/fgdata_git/Nasal/geo.nas, line 173
  called from: /devel/fgdata_git/Nasal/view.nas, line 306
called from: /devel/fgdata_git/Nasal/view.nas, line 265
called from: /devel/fgdata_git/Nasal/view.nas, line 217
called from: /devel/fgdata_git/Nasal/view.nas, line 719


with Fly-By View and Model-View   broken

Is it just me ?

Ahmad
--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] [Flightgear-commitlogs] SimGear branch, next, updated. 8e75c6be5047bdb0deacc385decc4ff4187c4990

[Thomas Geymayer]

2013/10/14 James Turner :
> +catch(...)
> +{
> +  naRuntimeError(c, "Unknown exception in method call.");
> +}
> +
>
> I am slightly concerned about catching all exceptions this way - I agree
> catching std::exception is worthwhile, with the specialisation for
> sg_exception since we can provide better logging and reporting, but I really
> hope no-one is throwing arbitrary objects not inheriting from
> std::exception. We used to have some bad cases of people throwing
> std::string but I cleaned those up years ago.

There are still some catch(...) and catch(std::string/const char*)
around... I just wanted to make sure that no exception will every pass
on to C space, as this leads to undefined behaviour and probably also
a crash. I don't know who will use cppbind to register whatever is
needed in the future, so I think its better to throw a Nasal runtime
error than to let the whole program crash.

Tom

--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] [Flightgear-commitlogs] SimGear branch, next, updated. 8e75c6be5047bdb0deacc385decc4ff4187c4990

[James Turner]

On 13 Oct 2013, at 12:04, Flightgear-commitlogs  
wrote:

> +catch(...)
> +{
> +  naRuntimeError(c, "Unknown exception in method call.");
> +}
> +

I am slightly concerned about catching all exceptions this way - I agree 
catching std::exception is worthwhile, with the specialisation for sg_exception 
since we can provide better logging and reporting, but I really hope no-one is 
throwing arbitrary objects not inheriting from std::exception. We used to have 
some bad cases of people throwing std::string but I cleaned those up years ago.

I guess it's not that this does any harm (except for more exception handling 
overhead, which is probably very low), I just dislike the idea such a thing is 
ever needed for us - it's not like we are calling into arbitrary plugin code 
which might throw anything.

Kind regards,
James

--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel