RE: [Flightgear-devel] Compile error latest CVS

> Behalf Of David Megginson > > Thanks -- I'll fix that tomorrow, if people don't mind waiting. It's > an ANSI/non-ANSI C++ thing. That would be great, David. Been very, very, busy today! And I am all smiles, now. Jon ___ Flightgear-devel mailing li

Re: [Flightgear-devel] VOR TO/FROM

- Original Message - From: "Alex Perry" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 10, 2002 10:09 PM Subject: Re: [Flightgear-devel] VOR TO/FROM > > Going thru the FG nav code for FG I noticed the To/From flag calculation in radiostack.cxx. > > I think it's ok;

Re: [Flightgear-devel] VOR TO/FROM

> Going thru the FG nav code for FG I noticed the To/From flag calculation in >radiostack.cxx. I think it's ok; you might be confusing the nav_heading variable with the aircraft_heading variable; the former is simply the actual radial. Using the latter would give the behavior you're implying.

Re: [Flightgear-devel] VOR TO/FROM

You are correct; I'll have to look at it too, now. > I believe the to/from is independent of aircraft heading and only denotes position >left or right of the orthogonal vector to the selected radial. ___ Flightgear-devel mailing list [EMAIL PROTECTED

Re: [Flightgear-devel] FreeGLUT

On Sun, Jan 06, 2002 at 10:34:46PM +, Ross Golder wrote: > It seems Mesa 4.0.1 doesn't come with glut, like 3.4. Has using freeglut > been discussed before? I couldn't find anything in the archives. > > > Besides being maintained upstream, are there any benefits to

[Flightgear-devel] VOR TO/FROM

Hi,   Going thru the FG nav code for FG I noticed the To/From flag calculation in radiostack.cxx.   Someone might want to check on the method of calculation.   I believe the to/from is independent of aircraft heading and only denotes position left or right of the orthogonal vector to the sel

RE: [Flightgear-devel] Re: ANSI C++ fixes; Compiling with G++ 3.x

David Megginson writes: > >Paul Deppe writes: > > > This same error occurs using the latest Cygwin on Win2000. > >Is that based on G++ 2.95 or G++ 3.0? 2.95 is what is distributed ! FWIW - I believe _G_LIB_VERSION is what really matters For Cygwin this is #define _G_LIB_VERSION "2.8.0" Cheer

RE: [Flightgear-devel] Compile error latest CVS

Bernie Bright writes: > >John Check wrote: >> >> Latest CVS build dies with following error >> >> make[4]: Entering directory >> `/home/j4strngs/Repository/FlightGear/src/FDM/JSBSim' >> c++ -DFGFS -I../../.. -I../../../src -I/usr/local/include >> -I/usr/X11R6/include -g -O2 -c FGTable.cpp >> F

re: [Flightgear-devel] Compile error latest CVS

John Check writes: > Latest CVS build dies with following error > > make[4]: Entering directory > `/home/j4strngs/Repository/FlightGear/src/FDM/JSBSim' > c++ -DFGFS -I../../.. -I../../../src -I/usr/local/include > -I/usr/X11R6/include -g -O2 -c FGTable.cpp > FGTable.cpp: In method `vo

RE: [Flightgear-devel] Re: ANSI C++ fixes; Compiling with G++ 3.x

Paul Deppe writes: > This same error occurs using the latest Cygwin on Win2000. Is that based on G++ 2.95 or G++ 3.0? All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flig

re: [Flightgear-devel] Re: ANSI C++ fixes; Compiling with G++ 3.x

Alex Romosan writes: > David Megginson <[EMAIL PROTECTED]> writes: > > > I've committed made four small ANSI C++ fixes to the CVS to allow > > FlightGear to compile with G++ 3.0.3. I'd appreciate it if porters > > could confirm that the changes don't break any legacy compilers. > > >

Re: [Flightgear-devel] Compile error latest CVS

John Check wrote: > > Latest CVS build dies with following error > > make[4]: Entering directory > `/home/j4strngs/Repository/FlightGear/src/FDM/JSBSim' > c++ -DFGFS -I../../.. -I../../../src -I/usr/local/include > -I/usr/X11R6/include -g -O2 -c FGTable.cpp > FGTable.cpp: In method `void FGTab

RE: [Flightgear-devel] Re: ANSI C++ fixes; Compiling with G++ 3.x

> > I've committed made four small ANSI C++ fixes to the CVS to allow > > FlightGear to compile with G++ 3.0.3. I'd appreciate it if porters > > could confirm that the changes don't break any legacy compilers. > > > > this breaks compiling with gcc 2.95.4. i get the following error (on a > debi

[Flightgear-devel] Compile error latest CVS

Latest CVS build dies with following error make[4]: Entering directory `/home/j4strngs/Repository/FlightGear/src/FDM/JSBSim' c++ -DFGFS -I../../.. -I../../../src -I/usr/local/include -I/usr/X11R6/include -g -O2 -c FGTable.cpp FGTable.cpp: In method `void FGTable::Print()': FGTable.cpp:228: `i

Re: [Flightgear-devel] Problems with JSBSim under Win32

On Thu, 2002-01-10 at 15:08, Geoff McLane wrote: > re: AVOID #QNAN > > > ... old problem in JSBSim, but ... MSVS only. Probably > = > > therefore nobody > > ... well a few ... slowly ... > > I changed FGAuxilary.cpp in the following - > > // Compare [d:\fg78cvs\flightgear\src\FDM\JSBSim\FGAu

[Flightgear-devel] Re: ANSI C++ fixes; Compiling with G++ 3.x

David Megginson <[EMAIL PROTECTED]> writes: > I've committed made four small ANSI C++ fixes to the CVS to allow > FlightGear to compile with G++ 3.0.3. I'd appreciate it if porters > could confirm that the changes don't break any legacy compilers. > this breaks compiling with gcc 2.95.4. i get

Re: [Flightgear-devel] Problems with JSBSim under Win32

re: AVOID #QNAN > ... old problem in JSBSim, but ... MSVS only. Probably = > therefore nobody ... well a few ... slowly ... I changed FGAuxilary.cpp in the following - // Compare [d:\fg78cvs\flightgear\src\FDM\JSBSim\FGAuxiliary.cpp] // Size: 9,166 25/12/01 09:01 // With[d:\fg7

Re: [Flightgear-devel] Simgear problem + Misc other stuff

Norman Vine wrote: > [snip] > > Well, I have mentioned this before anyway > > By changing the PPE main() into a function call say > int ppe ( ssgContext *ssg, ssgRoot *root, myFGFS *fgfs ) > > where myFGFS contains a few important vars such as lat lon and > ssgRoot is a scenery node and s

Re: [Flightgear-devel] Simgear problem + Misc other stuff

On Wednesday 9 January 2002 13:59, Kaiser Georg wrote: > -Original Message- > From: David Findlay [mailto:[EMAIL PROTECTED]] > Sent: Mittwoch, 09. Jänner 2002 12:07 > To: [EMAIL PROTECTED] > Subject: [Flightgear-devel] Simgear problem + Misc other stuff > > > EasyXML is missing from simgea

RE: [Flightgear-devel] Problems with JSBSim under Win32

This is old problem in JSBSim, but it has such fatal implications on executables compiled using MSVS only. Probably therefore nobody didn't try find it yet.. Try do next in "FGInitialCondition.cxx" to run it: bool FGInitialCondition::solve(float *y,float x) { float x1,x2,x3,f1,f2,f3,d,d0;

[Flightgear-devel] Problems with JSBSim under Win32

After initialization of the JSB-FDM and tying properties to the FGInterface the location (lon, lat, alt, ...) is lost (values are 1.#QNAN) so that FG runs into that: // schedule a needed buckets for loading void FGTileMgr::schedule_needed() { // sanity check (unfortunately nee

[Flightgear-devel] ANSI C++ fixes; Compiling with G++ 3.x

I've committed made four small ANSI C++ fixes to the CVS to allow FlightGear to compile with G++ 3.0.3. I'd appreciate it if porters could confirm that the changes don't break any legacy compilers. I think it's generally a good thing for developers to use G++ 3.x, since it is very picky about AN