Hi!
I was just trying to compile the latest release of FG, but I got a bunch
of errors. I notice the errors involve gcc 3.2 stdc++ headers, so maybe
I have used an unsupported version of gcc.
Some compiler error messages follow.
Thanks for this entertaining and interesting software.
Sydney Weidman writes:
I was just trying to compile the latest release of FG, but I got a bunch
of errors. I notice the errors involve gcc 3.2 stdc++ headers, so maybe
I have used an unsupported version of gcc.
Some compiler error messages follow.
Thanks for this entertaining and
On Sat, Sep 28, 2002 at 07:31:54AM -0500, Sydney Weidman wrote:
Hi!
I was just trying to compile the latest release of FG, but I got a bunch
of errors. I notice the errors involve gcc 3.2 stdc++ headers, so maybe
I have used an unsupported version of gcc.
Some compiler error messages
Norman Vine wrote:
Sydney Weidman writes:
I was just trying to compile the latest release of FG, but I got a bunch
of errors. I notice the errors involve gcc 3.2 stdc++ headers, so maybe
I have used an unsupported version of gcc.
Some compiler error messages follow.
Thanks for this
Simon Fowler wrote:
Make sure you've compiled all the libraries flightgear depends on
with the same compiler you built flightgear with (that includes
libmetakit, which is where I've seen problems). Not sure if you'd
see this with standard libraries, but I've definitely seen this with
I don't know if the man pages are being kept current, but I thought I
would point this out anyway.
The man page fgfs.1 lists FGROOT under environment variables, but the
program seems to want to use FG_ROOT.
Great program! Just wanted to contribute in some small way.
Regards,
Syd.
I just tried a fresh build and I noticed the control surface animations
aren't working. The prop animation works fine.
Also (this has been like this for a while) if I go to view mode
and change the view angle on the vertical axis then center the view
(shift+keypad8) the panel reappears but the
Ok, thanks for catching this! The fix is now in cvs.
Curt.
Sydney Weidman writes:
I don't know if the man pages are being kept current, but I thought I
would point this out anyway.
The man page fgfs.1 lists FGROOT under environment variables, but the
program seems to want to use
Julian Foad wrote:
Just trying my first CVS update in a couple of weeks. I see there is a
new repository for the trunk, so I changed all my CVS/Root files to
point to the -0.9 one and logged in with the new password. [Why not
just have no password?] But I get:
cvs server: Updating
I just installed the current development CVS for both SimGear and fgfs with
./config --with-threads and make and make install ok.
Also installed development CVS fgfsbase.
I did not update Plib from recent CVS. Still using plib-0.1.6.
Kernel is 2.4.18-10 RH7.3 and graphic card driver is
I just started with MSVC, but I recognize this one.
you have to use std::cout, because MSVC is anal about namespaces.
- Original Message -
From: Simon Fowler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 25, 2002 8:21 AM
Subject: Re: [Flightgear-devel] Compile error
I installed the latest development plib tar file and recompiled fgfs.
No change.
The last 2 lines before the freeze:
Cannot open file: /usr/local/FlightGear/Scenery/Objects.txt
Initializing splash screen
The splash screen displays and remains the active window.
But the systme is frozen.
Dave Perry writes:
I installed the latest development plib tar file and recompiled fgfs.
No change.
The last 2 lines before the freeze:
Cannot open file: /usr/local/FlightGear/Scenery/Objects.txt
Initializing splash screen
The splash screen displays and remains the active window.
But
I've just checked in a new pitot system and airspeed-indicator
instrument to FlightGear CVS. Here's how everything works:
1. The pitot system reads /environment/pressure-inhg (p),
/environment/density-slugft3 (r), and /velocities/uBody-fps (v).
It then calculates q (dynamic pressure) with
sleep 5m; killall fgfs; sleep 1m; killall -9 fgfs; sleep 1m; halt
should be executing on a root text console before you start the simulator.
I usually find that one of the two killall's will recover the machine.
A network login, of course, can do the same thing. However, you
generally need to
I did a bit of code shuffling with respect to the ExternalNet fdm and
moved it to it's own subdirectory.
The goal is to also include in that subdir some stand along FDM
wrapper apps that interface to FlightGear via the ExternalNet
interface. These would act as examples for people interested in
FWIW with the switch --disable-splash-screen, fgfs loads and runs ok.
Even with this switch, the splash screen displays, but no lock up.
-Dave
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
On Saturday, September 28, 2002, at 04:49 PM, Curtis L. Olson wrote:
I did a bit of code shuffling with respect to the ExternalNet fdm and
moved it to it's own subdirectory.
The goal is to also include in that subdir some stand along FDM
wrapper apps that interface to FlightGear via the
18 matches
Mail list logo
