not to make
> any difference, at least on my machine.
>
> Mark
>
> > -Original Message-
> > From: Curtis L. Olson [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 30, 2002 3:17 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [Flightgear-devel]
I tried it both ways under windows and it seems not to make
any difference, at least on my machine.
Mark
> -Original Message-
> From: Curtis L. Olson [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 30, 2002 3:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Flightgear-deve
Keith Wiley wrote:
>
> Something I've been wondering about. The program that comes with the
> downloadable binary is about 4 megs. The program that is built from cvs
> is about 56 megs. I have been having major framerate issues with the cvs
> version (2 or 3 fps) whereas the binary version run
Alex Perry writes:
> It has a symbol table so that the debugger would be useful.
> You can "strip" it, but it should have no impact on execution speed.
But perhaps could impact how fast the application is loaded. I
apologize if I am wrong, but I believe Linux does demand paging so it
really shou
Keith,
> Something I've been wondering about.
> The program that comes with the
> downloadable binary is about 4 megs.
> The program that is built from cvs
The exe produced via CVS has numerous debugging information. Use
strip fgfs.exe
to cut it down to normal size. (BTW, this is in the ma
It has a symbol table so that the debugger would be useful.
You can "strip" it, but it should have no impact on execution speed.
> Something I've been wondering about. The program that comes with the
> downloadable binary is about 4 megs. The program that is built from cvs
> is about 56 megs.
Something I've been wondering about. The program that comes with the
downloadable binary is about 4 megs. The program that is built from cvs
is about 56 megs. I have been having major framerate issues with the cvs
version (2 or 3 fps) whereas the binary version runs at 7 or 8 fps. I'm
trying t