Re: [Flightgear-devel] 3D HUD Support
Norman Vine wrote: Erik Hofman writes: I want to apply the 3D HUD patch which was originally written by Andy Ross and later modified by you. I understand and I am all for it :-) In fact the Win32 binary users already have this. It is the 'requires aircraft tobe repositioned' is what I was unclear about Oh, sorry. I have to rephrase it a little. If I apply the patch and start FlightGear using the F-16 the hud is positioned to far up, leaving the HUD area. This has to be fixed (and can be fixed), but other then the F-16 I have no authoroty over the aircraft section, so other people need to do that themselves. How does this work for the Win32 port, don't you see that problem? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] F16
Has anyone else noticed that the F16 rudder acts in the opposite direction to all other aircraft? Or is it just my system? Richard Bytheway ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Still linker error in today's FlightGear
Alex Romosan wrote: i see the same thing and i even made a distclean beforehand. anyway, looking at src/Include/config.h is see that both FG_MPLAYER_AS and FG_NETWORK_OLK are defined. shouldn't the new multiplayer mode disable the old network code? Yes it should. Turns out to be my bad. I had --without-network-olk defined in my configure script, so I didn't notice :-( It is updated in CVS now. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Still linker error in today's FlightGear
Martin Spott wrote: Oh, I'm no more a newbie in pushing other people's stuff through the compiler ;-) Just checking .. I even remade the whole build directory (including those of metakit, plib and SimGear). You can assume that I built everything from current CVS before reporting an error. Obviously some of the linker errors I posted result of missing references in the NetworkOLK stuff. Probably something resides outside the NetworkOLK directory and now it misses references because it does not get disabled at compile time like the rest of this stuff. I'll see what happens if I include NetworkOLK, Yes, My bad (see my other post about this issue). A fix is in CVS now. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Still linker error in today's FlightGear
Jonathan Polley wrote: In my case, I don't want any of the multi-pilot code in my build. For some reason, as of yesterday, src/MultiPlayer is required for the build (--with-network is defaulted to yes). If it requires that I build with --with-network-olk then this is a very bad thing (IMHO) because I don't believe that code works on all platforms. At the very least, it would be nice if all the required switches were defaulted to the same values. The patch was delivered without the abilitty to disable it all together. I've updated the code to be able to compile without it, but unfortunately that's where something went wrong (see my other post about it). Actually after the chaneg NetworkOLK should be disabled by default, but due to a slight problem in configure this went wrong. It is fixed in CVS now. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Still linker error in today's FlightGear
On Thursday, March 20, 2003, at 11:26 pm, Martin Spott wrote: Oh, I'm no more a newbie in pushing other people's stuff through the compiler ;-) I even remade the whole build directory (including those of metakit, plib and SimGear). You can assume that I built everything from current CVS before reporting an error. I'm in exactly the same boat as Martin, I have cvs update and rebuilt everything, including a distclean in FlightGear/. The only option I'm passing to configure is --with-threads. Obviously some of the linker errors I posted result of missing references in the NetworkOLK stuff. Probably something resides outside the NetworkOLK directory and now it misses references because it does not get disabled at compile time like the rest of this stuff. I'll see what happens if I include NetworkOLK, Just tried: ./configure --with-threads --with-network-olk And got the same link errors as Martin has been reporting. Any clues? H&H James -- That which does not kill me has poor aim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Screenshots: Curt's scenery improvements
Jon Stockill writes: > Wow, looks likt there's some real detail in there. What's the global > coverage like for this data? The current UK DEM data is rather coarse, > resulting in very flat terrain - I'm guessing there'll be huge > improvements if the UK SRTM data has been released? I expect you'll see exactly the same improvement I did for Canadian scenery: http://www.megginson.com/flightsim/old-scenery.png http://www.megginson.com/flightsim/new-scenery.png I don't know when they're planning to release the 3 arcsec SRTM data for areas outside North America, but then, until a few days ago I hadn't known that the Canadian data were available. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] 3D HUD Support
Erik Hofman writes: > > Norman Vine wrote: > > Erik Hofman writes: > > >>I want to apply the 3D HUD patch which was originally written by Andy > >>Ross and later modified by you. > > > > > > I understand and I am all for it :-) > > In fact the Win32 binary users already have this. > > > > It is the 'requires aircraft tobe repositioned' is what I was > unclear about > > Oh, sorry. I have to rephrase it a little. > If I apply the patch and start FlightGear using the F-16 the hud is > positioned to far up, leaving the HUD area. This has to be fixed (and > can be fixed), but other then the F-16 I have no authoroty over the > aircraft section, so other people need to do that themselves. > > How does this work for the Win32 port, don't you see that problem? Yes but I think this is what Andy intended ie the 3D HUD is alligned with the horizon As long as you are making the adjustments outside of the actual HUD 'C' code feel free to make any changes you want e.g. We don't want any model specific code, reading a possibly new property is certainly OK though Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] 3D HUD Support
Norman Vine wrote: If I apply the patch and start FlightGear using the F-16 the hud is positioned to far up, leaving the HUD area. This has to be fixed (and can be fixed), but other then the F-16 I have no authoroty over the aircraft section, so other people need to do that themselves. How does this work for the Win32 port, don't you see that problem? > Yes but I think this is what Andy intended ie the 3D HUD is alligned with the horizon That is what mean, all the current HUD's need to be realligned ebcause of this change. As long as you are making the adjustments outside of the actual HUD 'C' code feel free to make any changes you want e.g. We don't want any model specific code, reading a possibly new property is certainly OK though That is one of the things I want to look at some time, instead of specifi hud card ladders, create one ladder wit a property input. I also want to add property support to labels. This should make the HUD core much more flexible already. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Still linker error in today's FlightGear
Erik Hofman <[EMAIL PROTECTED]> wrote: > A fix is in CVS now. Not bad Thanks, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [PATCH] for cvs
It probably gets through undetected when configured --without-logging
Cheers - Dave
On 3/20/03 at 11:30 PM Erik Hofman wrote:
>Ironhell3 . wrote:
>> ok, i am not sure if this is correct but this way compiles cvs version
>> of Flightgear
>
>Shoot. You are right.
>Funny I didn't catch that one.
>
>Thanks.
>
>Erik
>
>>
>> --- src/Main/fg_init.cxx2003-03-20 14:33:11.0 +0200
>> +++ src/Main/fg_init.new.cxx2003-03-20 14:32:58.0 +0200
>> @@ -740,5 +740,5 @@
>> SG_LOG( SG_GENERAL, SG_INFO,
>> "Attempting to set starting position for "
>> -<< id << ":" << runway );
>> +<< id << ":" << rwy );
>>
>> if ( ! runways.search( id, rwy, &r ) ) {
>>
>>
>> For any replies please CC me cause i am not on the list.I bieleve this
>> was just i typo?
>>
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] 3D HUD Support
Erik Hofman wrote: Norman Vine wrote: Yes but I think this is what Andy intended ie the 3D HUD is alligned with the horizon That is what mean, all the current HUD's need to be realligned ebcause of this change. It looks like just three HUD types are used, the default, a custom default and the F-16 HUD. I think I go ahead and commit it to CVS. We must be able to overcome this problem. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [PATCH] for cvs
David Luff wrote: It probably gets through undetected when configured --without-logging I'm using default settings now, except for threading. Things should work out better in the future. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] F16
Richard Bytheway wrote: Has anyone else noticed that the F16 rudder acts in the opposite direction to all other aircraft? I've never noticed it and it should be right. Does anybody else notice this? Or is it just my system? I can't possibly think of a way that makes it system specific? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Hi-Res C172-S Instrument panel
Martin Dressler just sent me his hi-res Bendix-King HSI which rounds out the C172-S instrument panel. This panel is designed to run full screen and sit next to a physical radio stack so it's not complete in and of itself, but it is a beautiful sight to see. Martin does really nice work. Screen shot: http://www.flightgear.org/tmp/c172s-panel.jpg Live action (cvs base package): ./fgfs --aircraft=c172-610x-jsbsim If you try this, you can toggel the panel to see the outside world ... or just hook up a 2nd PC for the outside visuals. :-) Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Photo Texture Generation Problems
Hi, I have downloaded and have run FlightGear Scenery Designer which runs really well. I have loaded a Satellite image from geoengine.nima.mil into the designer which again works really well. It was only then that I realised that FGSD doesn't export the images to the output directory. So back to command line utils. I guess the tool that I need to use is 'photo' in 'prep' in TerraGear. The command line that I run is: ./photo ./output ../../nimadata1048254311.jpg 16 16 -3.31 53.55 -3.31 53.23 -2.69 53.23 -2.69 53.55 but the files it generates aren't what I expected. I get files with numeric file names containing hole information. I was expecting to get the rgb files, etc as per the KSJC example download. I may be running the wrong tool or have misinterpreted the command line options. Can anyone please give me some guidance. Many thanks, in anticipation. Dave = Tel: +44 (0) 7092 250 375 Fax: +44 (0) 7092 250 375 __ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main main.cxx,1.62,1.63
Erik Hofman <[EMAIL PROTECTED]> wrote: > Update of /var/cvs/FlightGear-0.9/FlightGear/src/Main > In directory seneca:/tmp/cvs-serv12094/src/Main > Modified Files: > main.cxx > Log Message: > Andy wrote: > This is just a port of an old 3D HUD patch to the new view code. Oh yeah, this looks really crisp _and_ complete without enabling "anti-alias-hud". I have the impression it also consumes noticeable less CPU power than the anti-aliased HUD I had to use before. As you already mentioned the HUD ladder needs to be compressed, but also the witdh of the new HUD is a bit larger as the default FG window: The 'power' gauge leaves the window to the left. Anyway a very nice improvement, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: F16
Erik Hofman <[EMAIL PROTECTED]> writes: > Richard Bytheway wrote: >> Has anyone else noticed that the F16 rudder acts in the opposite >> direction to all other aircraft? > > I've never noticed it and it should be right. Does anybody else > notice this? For me the rudder is fine but the nose gear steering is reversed. -- Istvan ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Compile error in latest cvs
I'm running gcc-2.95.4. In the latest cvs, the compile bombs here: make[3]: Entering directory `/home/curt/projects/FlightGear-0.9/FlightGear/src/Cockpit' source='cockpit.cxx' object='cockpit.o' libtool=no \ depfile='.deps/cockpit.Po' tmpdepfile='.deps/cockpit.TPo' \ depmode=gcc /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X11R6/include -Wall -O2 -D_REENTRANT -c -o cockpit.o `test -f cockpit.cxx || echo './'`cockpit.cxx In file included from cockpit.cxx:55: hud.hxx: In method `void fgLineList::draw()': hud.hxx:380: implicit declaration of function `int for_each(...)' make[3]: *** [cockpit.o] Error 1 I'm flying out to Los Angeles this coming week and I *really* need to have a working cvs build before I go Am I the only one that is seeing this problem?!? Thanks, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile error in latest cvs
On Fri, 2003-03-21 at 12:57, Curtis L. Olson wrote: > I'm running gcc-2.95.4. In the latest cvs, the compile bombs here: > > make[3]: Entering directory > `/home/curt/projects/FlightGear-0.9/FlightGear/src/Cockpit' > source='cockpit.cxx' object='cockpit.o' libtool=no \ > depfile='.deps/cockpit.Po' tmpdepfile='.deps/cockpit.TPo' \ > depmode=gcc /bin/sh ../../depcomp \ > g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src > -I/usr/X11R6/include -Wall -O2 -D_REENTRANT -c -o cockpit.o `test -f cockpit.cxx || > echo './'`cockpit.cxx > In file included from cockpit.cxx:55: > hud.hxx: In method `void fgLineList::draw()': > hud.hxx:380: implicit declaration of function `int for_each(...)' > make[3]: *** [cockpit.o] Error 1 > > I'm flying out to Los Angeles this coming week and I *really* need to > have a working cvs build before I go Am I the only one that is > seeing this problem?!? I did a fresh CVS checkout of plib, SimGear and fgfs and compiled about 11:00CST this morning. I didn't see this error then. William -- William L. Riley [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile error in latest cvs
From: "Curtis L. Olson" : > I'm running gcc-2.95.4. In the latest cvs, the compile bombs here: > > make[3]: Entering directory `/home/curt/projects/FlightGear-0.9/FlightGear/src/Cockpit' > source='cockpit.cxx' object='cockpit.o' libtool=no \ > depfile='.deps/cockpit.Po' tmpdepfile='.deps/cockpit.TPo' \ > depmode=gcc /bin/sh ../../depcomp \ > ++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X 11R6/include -Wall -O2 -D_REENTRANT -c -o cockpit.o `test -f cockpit.cxx || echo './'`cockpit.cxx > In file included from cockpit.cxx:55: > hud.hxx: In method `void fgLineList::draw()': > hud.hxx:380: implicit declaration of function `int for_each(...)' > make[3]: *** [cockpit.o] Error 1 > > I'm flying out to Los Angeles this coming week and I *really* need to > have a working cvs build before I go Am I the only one that is > seeing this problem?!? Do you need SG_USING_STD( for_each ) ? -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile error in latest cvs
Frederic Bouvier writes: > From: "Curtis L. Olson" : > > I'm running gcc-2.95.4. In the latest cvs, the compile bombs here: > > > > make[3]: Entering directory > `/home/curt/projects/FlightGear-0.9/FlightGear/src/Cockpit' > > source='cockpit.cxx' object='cockpit.o' libtool=no \ > > depfile='.deps/cockpit.Po' tmpdepfile='.deps/cockpit.TPo' \ > > depmode=gcc /bin/sh ../../depcomp \ > > > ++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X > 11R6/include -Wall -O2 -D_REENTRANT -c -o cockpit.o `test -f cockpit.cxx || > echo './'`cockpit.cxx > > In file included from cockpit.cxx:55: > > hud.hxx: In method `void fgLineList::draw()': > > hud.hxx:380: implicit declaration of function `int for_each(...)' > > make[3]: *** [cockpit.o] Error 1 > > > > I'm flying out to Los Angeles this coming week and I *really* need to > > have a working cvs build before I go Am I the only one that is > > seeing this problem?!? > > Do you need SG_USING_STD( for_each ) ? It looks like what I really needed was #include Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hi-Res C172-S Instrument panel
> Martin Dressler just sent me his hi-res Bendix-King HSI which rounds > out the C172-S instrument panel. This panel is designed to run full > screen and sit next to a physical radio stack so it's not complete in > and of itself, but it is a beautiful sight to see. Martin does really > nice work. Fantastic, this plane is better than ever for IFR training (though tuning the radios via the menu is a bit painful, especially if the mouse is the yoke substitute for lack of dedicated hardware...). Just two questions: I assume that this HSI uses an ADAHRS rather than a gyro, otherwise it would have to be calibrated, and I can't see a calibration knob anywhere. What North does it point to then? Also, if I use the AP in heading mode, why don't any two of the three headings (HSI, HUD, AP buck) coincide? I just tried flying (out of KSFO) with the buck set to 360. HUD shows 356.5, HSI is on 342. I thought the AP would just centre the buck, but that doesn't seem to be the case. Any ideas? Andras === Major Andras e-mail: [EMAIL PROTECTED] www:http://andras.webhop.org/ === ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile error in latest cvs
From: "Curtis L. Olson" : > Frederic Bouvier writes: > > From: "Curtis L. Olson" : > > > I'm running gcc-2.95.4. In the latest cvs, the compile bombs here: > > > > > > make[3]: Entering directory > > `/home/curt/projects/FlightGear-0.9/FlightGear/src/Cockpit' > > > source='cockpit.cxx' object='cockpit.o' libtool=no \ > > > depfile='.deps/cockpit.Po' tmpdepfile='.deps/cockpit.TPo' \ > > > depmode=gcc /bin/sh ../../depcomp \ > > > > > + -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X > > 11R6/include -Wall -O2 -D_REENTRANT -c -o cockpit.o `test -f cockpit.cxx || > > echo './'`cockpit.cxx > > > In file included from cockpit.cxx:55: > > > hud.hxx: In method `void fgLineList::draw()': > > > hud.hxx:380: implicit declaration of function `int for_each(...)' > > > make[3]: *** [cockpit.o] Error 1 > > > > > > I'm flying out to Los Angeles this coming week and I *really* need to > > > have a working cvs build before I go Am I the only one that is > > > seeing this problem?!? > > > > Do you need SG_USING_STD( for_each ) ? > > It looks like what I really needed was #include Now that I have updated CVS, I see the same thing with MSVC -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile error in latest cvs
Curtis L. Olson writes: > > I'm running gcc-2.95.4. In the latest cvs, the compile bombs here: > > make[3]: Entering directory > `/home/curt/projects/FlightGear-0.9/FlightGear/src/Cockpit' > source='cockpit.cxx' object='cockpit.o' libtool=no \ > depfile='.deps/cockpit.Po' tmpdepfile='.deps/cockpit.TPo' \ > depmode=gcc /bin/sh ../../depcomp \ > g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. > -I../../src -I/usr/X11R6/include -Wall -O2 -D_REENTRANT -c -o > cockpit.o `test -f cockpit.cxx || echo './'`cockpit.cxx > In file included from cockpit.cxx:55: > hud.hxx: In method `void fgLineList::draw()': > hud.hxx:380: implicit declaration of function `int for_each(...)' > make[3]: *** [cockpit.o] Error 1 Deja view http://www.menet.umn.edu/~curt/lists/fgfs/archive-200212/msg00169.html Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile error in latest cvs
Norman Vine writes: > Curtis L. Olson writes: > > > > I'm running gcc-2.95.4. In the latest cvs, the compile bombs here: > > > > make[3]: Entering directory > > `/home/curt/projects/FlightGear-0.9/FlightGear/src/Cockpit' > > source='cockpit.cxx' object='cockpit.o' libtool=no \ > > depfile='.deps/cockpit.Po' tmpdepfile='.deps/cockpit.TPo' \ > > depmode=gcc /bin/sh ../../depcomp \ > > g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. > > -I../../src -I/usr/X11R6/include -Wall -O2 -D_REENTRANT -c -o > > cockpit.o `test -f cockpit.cxx || echo './'`cockpit.cxx > > In file included from cockpit.cxx:55: > > hud.hxx: In method `void fgLineList::draw()': > > hud.hxx:380: implicit declaration of function `int for_each(...)' > > make[3]: *** [cockpit.o] Error 1 > > Deja view > http://www.menet.umn.edu/~curt/lists/fgfs/archive-200212/msg00169.html Well in this case someone actually added a call to for_each() in hud.hxx, but otherwise very similar symptoms. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile error in latest cvs
From: "Frederic Bouvier" <[EMAIL PROTECTED]> > From: "Curtis L. Olson" : > > Frederic Bouvier writes: > > > From: "Curtis L. Olson" : > > > > I'm running gcc-2.95.4. In the latest cvs, the compile bombs here: > > > > > > > > make[3]: Entering directory > > > `/home/curt/projects/FlightGear-0.9/FlightGear/src/Cockpit' > > > > source='cockpit.cxx' object='cockpit.o' libtool=no \ > > > > depfile='.deps/cockpit.Po' tmpdepfile='.deps/cockpit.TPo' \ > > > > depmode=gcc /bin/sh ../../depcomp \ > > > > > > > > -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X > > > 11R6/include -Wall -O2 -D_REENTRANT -c -o cockpit.o `test -f > cockpit.cxx || > > > echo './'`cockpit.cxx > > > > In file included from cockpit.cxx:55: > > > > hud.hxx: In method `void fgLineList::draw()': > > > > hud.hxx:380: implicit declaration of function `int for_each(...)' > > > > make[3]: *** [cockpit.o] Error 1 > > > > > > > > I'm flying out to Los Angeles this coming week and I *really* need to > > > > have a working cvs build before I go Am I the only one that is > > > > seeing this problem?!? > > > > > > Do you need SG_USING_STD( for_each ) ? > > > > It looks like what I really needed was #include > > Now that I have updated CVS, I see the same thing with MSVC In fact, no, it is not the same. MSVC is having problem with SG_USING_STD(for_each). There is already a SG_USING_NAMESPACE(std). Could you please remove the line containing SG_USING_STD(for_each). Thanks -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile error in latest cvs
Frederic Bouvier writes: > In fact, no, it is not the same. MSVC is having problem with > SG_USING_STD(for_each). There is already a SG_USING_NAMESPACE(std). > > Could you please remove the line containing SG_USING_STD(for_each). Should all of the SG_USING_STD() lines be removed? gcc-2.95.4 ignores this directive so they don't affect me either way. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile error in latest cvs
From: "Curtis L. Olson" <[EMAIL PROTECTED]> > Frederic Bouvier writes: > > In fact, no, it is not the same. MSVC is having problem with > > SG_USING_STD(for_each). There is already a SG_USING_NAMESPACE(std). > > > > Could you please remove the line containing SG_USING_STD(for_each). > > Should all of the SG_USING_STD() lines be removed? gcc-2.95.4 ignores > this directive so they don't affect me either way. The other SG_USING_STD() lines are useless but are harmless. For MSVC, you can remove all and keep SG_USING_NAMESPACE(std) Thanks, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile error in latest cvs
Curtis L. Olson writes: > > Norman Vine writes: > > Curtis L. Olson writes: > > > > > > > Deja view > > http://www.menet.umn.edu/~curt/lists/fgfs/archive-200212/msg00169.html > > Well in this case someone actually added a call to for_each() in > hud.hxx, but otherwise very similar symptoms. Exactly this stems from the old patch of mine that Eric just added to have both the 2D and the 3D HUDs. The solution is the same now as then :-) Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Fw: [PATCH] missing logstream.hxx in weatherCM
Erik, I tried to send this message directly to you but it bounced, so I post this to the list. Cheers, -Fred - Original Message - From: "Frederic Bouvier" <[EMAIL PROTECTED]> To: "Erik Hofman" <[EMAIL PROTECTED]> Sent: Friday, March 21, 2003 9:55 PM Subject: [PATCH] missing logstream.hxx in weatherCM > Hello Erik, > > SG_LOG is not known in weatherCM and there is a missing comma. > This is to compile with MSVC > > Cheers, > -Fred > > D:\FlightGear\cvs\FlightGear\src>cvs diff -u WeatherCM > cvs server: Diffing WeatherCM > Index: WeatherCM/linintp2.cpp > === > RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/WeatherCM/linintp2.cpp,v > retrieving revision 1.3 > diff -u -r1.3 linintp2.cpp > --- WeatherCM/linintp2.cpp 20 Mar 2003 10:43:06 - 1.3 > +++ WeatherCM/linintp2.cpp 21 Mar 2003 20:52:39 - > @@ -31,6 +31,7 @@ > > #include > #include STL_IOSTREAM > +#include > > #include > #include > @@ -405,7 +406,7 @@ > } > > // create the triangles > -SG_LOG(SG_MATH, SG_DEBUG "[ 60%] create the triangles"); > +SG_LOG(SG_MATH, SG_DEBUG, "[ 60%] create the triangles"); > > triangle = new Triangle[numTriangles]; > > Index: WeatherCM/sphrintp.cpp > === > RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/WeatherCM/sphrintp.cpp,v > retrieving revision 1.3 > diff -u -r1.3 sphrintp.cpp > --- WeatherCM/sphrintp.cpp 20 Mar 2003 10:43:06 - 1.3 > +++ WeatherCM/sphrintp.cpp 21 Mar 2003 20:52:40 - > @@ -31,6 +31,7 @@ > > #include > #include STL_IOSTREAM > +#include > > #include > #include "sphrintp.h" > ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/WeatherCM linintp2.cpp,1.3,1.4 sphrintp.cpp,1.3,1.4
Erik, There is still a missing comma in line 409 of linintp2.cpp. -Fred D:\FlightGear\cvs\FlightGear\src>cvs diff -u WeatherCM cvs server: Diffing WeatherCM Index: WeatherCM/linintp2.cpp === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/WeatherCM/linintp2.cpp,v retrieving revision 1.4 diff -u -r1.4 linintp2.cpp --- WeatherCM/linintp2.cpp 21 Mar 2003 21:12:12 - 1.4 +++ WeatherCM/linintp2.cpp 21 Mar 2003 21:46:35 - @@ -406,7 +406,7 @@ } // create the triangles -SG_LOG(SG_MATH, SG_DEBUG "[ 60%] create the triangles"); +SG_LOG(SG_MATH, SG_DEBUG, "[ 60%] create the triangles"); triangle = new Triangle[numTriangles]; - Original Message - From: "Erik Hofman" > Update of /var/cvs/FlightGear-0.9/FlightGear/src/WeatherCM > In directory seneca:/tmp/cvs-serv24858/src/WeatherCM > > Modified Files: > linintp2.cpp sphrintp.cpp > Log Message: > Add logstream header files when using SG_LOG() ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Disabling the 3D Panel
Now that I have FlightGear linking, I have found another problem that has cropped up recently (I'm not sure when, exactly). It seems as if the 3D panel is always active. Since I always run FlightGear with the --disable-panel in my .fgfsrc file, this causes problems. If I don't run with --disable-panel, I get the same behavior. I have verified that options.cxx still processes --disable-panel. If I toggle the 2D panel from within FlightGear, I get the 2D panel placed in front of the 3D panel. Jonathan Polley ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
