Norman Vine wote:
! #ifdef _WIN32
#define snprintf _snprintf
#endif
--- 66,72
! #if defined(_WIN32) !defined(__CYGWIN__)
#define snprintf _snprintf
#endif
To Norman: Good fix.
To Curt (etc.): Shouldn't this go in simgear/compiler.h instead of in every source
file
David Megginson wrote:
Julian Foad writes:
No - we have that in some places, but I was thinking recently that it's
not the right way to go. I think the only practical purpose is to
reduce clutter in the browser; but the property browser could and should
do this for us if we
Oops - the link to Bleeding-edge CVS snapshot on the Flight Gear Downloads web page
points to repository version 0.7!
- Julian
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Andy Ross wrote:
John Check wrote:
What it is is that when electrical system modeling was added it
affected planes for which no electrical system was added.
Shouldn't the sane choice for the defaults be the opposite? The
instruments work unless the electrical system tells them that
Curtis Olson wrote:
The big thing that would need to be looked at is if we can include
based on the contents of a property name, rather than just include
some hard coded file name.
Like:
int main() {
char *sFile = getenv(FGFS_LANG);
char *LangStrings[] = {
#include sFile
}
...
Jon Berndt wrote:
The motion hardware has 2 degrees of freedom. Last night we had a
discussion on
what data to use from the sim (angular accelerations, velocities,
pitch, roll
etc.) and how to apply it to the motion hardware.
Also, if I recall correctly, the space shuttle motion
David Megginson wrote:
/instrumentation/altimeter/
/instrumentation/airspeed-indicator/
/instrumentation/vor-gauge/
/instrumentation/transponder/
etc., with indexes as appropriate. Inside each branch, we have a
collection of properties, some common to many (or all) instruments,
Jonathan Polley wrote:
Along the lines of adding the -pedantic option, I would like to add an
ability (probably at ./configure time) to specify additional compile
options. Since one of my platforms is a Mac, I would like to be able to
add -wno_long_double, as it keeps telling me that
The result of trying to view viewmgr.cxx (web page
http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/FlightGear/src/Main/viewmgr.cxx?rev=1.18cvsroot=FlightGear-0.7content-type=text/vnd.viewcvs-markup)
is the following error:
Failure during use of an external program:
enscript --color -W
Curtis L. Olson wrote:
It looks like enscript is breaking on viewmgr.cxx
Is it enscript that is breaking, or the other end of its pipe? The error message says
Broken pipe in enscript.write(chunk). Maybe just that the disk is full?
Does this happen with any other source files or is it
Curtis L. Olson wrote:
David Luff writes:
Unfortunately, when ./configure gets run automatically after typing
make, the configure switches after ./configure get remembered, but
the flags in front of ./configure don't (this is using Cygwin Bash). Is
there any way round this?
I've
Curtis L. Olson wrote:
[EMAIL PROTECTED] writes:
Is it enscript that is breaking, or the other end of its pipe? The
error message says Broken pipe in enscript.write(chunk). Maybe
just that the disk is full?
By my reading of the error message, python is reporting that enscript
died
Jim Wilson wrote:
Andy Ross [EMAIL PROTECTED] said:
Jim Wilson wrote:
On further investigation, it appears that this is almost certainly due to
normal variation in fdm position and orientation output.
This theory doesn't work though. Think about it: in cockpit mode, the
I don't mind either way.
I have found it generally useful to have them provided, and have wished the plib would
do the same (for .deps directories, in particular).
However, I have only ever worked on small patches, never adding files, so I have never
needed to take note of the ? and unknown
FYI
the FlightGear 'configure' is designed to be able to be run in
a directory other then then the CVS source tree.
That sounds well worth a try. Thanks.
This has several advantages amongst them keeping the source
tree MUCH cleaner :-)
And being able to keep a debug build and a release
There are two aspects to being on the glide slope. First, are you on _any_ path
that ends up at the beginning of the runway? Second, are you on the _intended_ glide
slope?
For the first, I was taught to look at the intended landing spot and, being aware of
the windscreen, see whether that
from:David Megginson [EMAIL PROTECTED]
date:Tue, 18 Jun 2002 14:53:00
to: [EMAIL PROTECTED]
subject: Re: [Flightgear-devel] static variables
Curt and I have discussed this before (either online or offline). We
could certainly have per-vehicle subtrees, i.e.
...
and
Keith, unfortunately Eric's instructions weren't quite right :(
Erik Hofman wrote:
Just do ./configure
this will give a full list of the possibilities.
He meant
./configure --help
of course :)
Yours is: --disable-logging
Actually, it is --without-logging:
./configure
Well I am happy to report that I got the Photo scenery to work perfectly.
Unfortunately it is with the latest windows binaries under XP. Although the
photo scenery works fine none of the other scenery seems to be installable
as it doesnt seem to be uncompressable under windows.
Do you mean
19 matches
Mail list logo
