Selon bass pumped :
On 9/22/05, Frederic Bouvier wrote:
Selon bass pumped :
Hi everyone,
I tried to compile the latest version of flightgear today in MSVC 7.
It compiled fine... but then I had problems when it tried linking.
Any ideas on how to fix it would help.
Thank
Selon bass pumped :
Hi everyone,
I tried to compile the latest version of flightgear today in MSVC 7.
It compiled fine... but then I had problems when it tried linking.
Any ideas on how to fix it would help.
Thank you in advance.
Start ouput
Linking...
LINK : warning LNK4075:
On 9/22/05, Frederic Bouvier [EMAIL PROTECTED] wrote:
Selon bass pumped :
Hi everyone,
I tried to compile the latest version of flightgear today in MSVC 7.
It compiled fine... but then I had problems when it tried linking.
Any ideas on how to fix it would help.
Thank you in
Hi everyone,
I tried to compile the latest version of flightgear today in MSVC 7.
It compiled fine... but then I had problems when it tried linking.
Any ideas on how to fix it would help.
Thank you in advance.
Start ouput
Linking...
LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to
--- PJ Quirk [EMAIL PROTECTED] wrote:
snip
you can see from the
screenshot:
http://www.cs.unc.edu/~quirk/blankscreen.bmp
Though the hud/panel can be displayed, and any
airplane flies fine
according to the instruments, there's just no
scenery.
snip
Patrick,
v0.9.8 comes with
On Wednesday 14 September 2005 14:36, Mike Rawlins wrote:
v0.9.8 comes with scenery for the 10x10 degree block
with corner 130W, 30N. Did you start the sim at KSFO?
If you started it in a region outside of central
California no scenery will show.
You're right, of course - but you should
Mike Rawlins wrote:
Patrick,
v0.9.8 comes with scenery for the 10x10 degree block
with corner 130W, 30N. Did you start the sim at KSFO?
If you started it in a region outside of central
California no scenery will show.
Mike
I didn't modify anything in the base package from the website, and
From: Andy Ross [EMAIL PROTECTED]
snip
These words, the same thing say.
Hmmm, too much of Star Wars prequel this summer have you watch? ;-)
Best,
Jim Wilson
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
On 9/7/05, Jim Wilson [EMAIL PROTECTED] wrote:
From: Andy Ross [EMAIL PROTECTED]
snip
These words, the same thing say.
Hmmm, too much of Star Wars prequel this summer have you watch? ;-)
Best,
Jim Wilson
LOL!!
___
Flightgear-devel
On 9/6/05, Andy Ross [EMAIL PROTECTED] wrote:
This looks like a version skew problem. That function
signature (with four arguments) is the one from the current CVS
version. The 0.9.8 Nasal interpreter used a different API with
only two arguments.
It looks to me like you're compiling CVS
bass pumped wrote:
Andy Ross wrote:
It looks to me like you're compiling CVS FlightGear with an older
SimGear.
I did download flightgear [...] from the 'bleeding edge' link from the
website. [...] But when compiling that simgear [...] I downloaded the
0.3.8 version.
Could that be a
On 9/6/05, Andy Ross [EMAIL PROTECTED] wrote:
bass pumped wrote:
Andy Ross wrote:
It looks to me like you're compiling CVS FlightGear with an older
SimGear.
I did download flightgear [...] from the 'bleeding edge' link from the
website. [...] But when compiling that simgear [...] I
bass pumped wrote:
Actually I was asking you (indirectly I guess) if there was an error
in the bleeding edge file I downloaded from the simgear download
page. Anyway, I will try compiling that by removing the couds3d
from the solution explorer and see what happens.
I'm not sure what you
bass,
I had the same error when 9.8 was first released. Working from lame memory
on the fix now, but I may be able to point you in the right direction.
Seems like I had to change the project settings under Configuration
Properties--C/C++--Advanced--Calling Convention. The right setting is
Another thought:
Struct Member Alignment, under Code Generation.
JA
Seems like I had to change the project settings under Configuration
Properties--C/C++--Advanced--Calling Convention. The right setting is
probably _cdecl (/Gd). You'll probably want to make sure all subprojects
share that
bass pumped wrote:
I'm trying to get flightgear 9.8 built in Windows. I'm using MSVC 7
for the build. I ran into the following errors from the Nasal code.
[...]
cannot convert from 'naRef (__cdecl*)(naContext,naRef,int,naRef *)' to
'naCFunction'
This looks like a version skew problem.
-Original Message-
From: [EMAIL PROTECTED] [mailto:flightgear-devel-
[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 7:01 PM
To: flightgear-devel@flightgear.org
Subject: [Flightgear-devel] MSVC error - glut32.lib
I am trying to compile FG on
'
Subject: RE: [Flightgear-devel] MSVC error - glut32.lib
-Original Message-
From: [EMAIL PROTECTED] [mailto:flightgear-devel-
[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 7:01 PM
To: flightgear-devel@flightgear.org
Subject: [Flightgear-devel] MSVC
Ben Morrison wrote:
I have downloaded the following source code files: FlightGear 9.8,
SimGear 3.8, plib 1.8.4, and zlib 1.1.4. I was able to get this to
compile in Visual Studio 2003 but when I try to run flight gear with
the following command: fgfs fg-root=c:\\GS_PTT\\Flightgear\\data
Harald JOHNSEN wrote :
Ben Morrison wrote:
I have downloaded the following source code files: FlightGear 9.8,
SimGear 3.8, plib 1.8.4, and zlib 1.1.4. I was able to get this to
compile in Visual Studio 2003 but when I try to run flight gear with
the following command: fgfs
Thanks, guys. This is my first time posting to the board and I am impressed
with the response times. I am compiling in debug mode because I am going to
be modifying flightgear later. Ok, Harald's solution fixed the runtime
error but now flightgear just sits there and doesn't start. What could
Ben Morrison wrote:
Thanks, guys. This is my first time posting to the board and I am impressed
with the response times. I am compiling in debug mode because I am going to
be modifying flightgear later. Ok, Harald's solution fixed the runtime
error but now flightgear just sits there and doesn't
It's not very clear. Check that you added the
'--fg-root=x:\flightgear\data' parameter to the debugger, not finding
the airports/runway data can lead FG to an infinite loop for example. Or
just press break and look where he is in the code ;)
Harald.
Ok, it turns out it was initializing it
Wow, it works! Thanks a lot for your help...
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de Frederic
Bouvier
Envoyé : jeudi 9 décembre 2004 20:31
À : FlightGear developers discussions
Objet : RE: [Flightgear-devel] MSVC
Selon RENNUIT Antoine 203220
That works better, but I still have several errors :
- what is fadmin project useful for? The true question is can I
remove it, because it needs FLTK, and it's a painful task to install it
correctly (no .lib, no .dll...).
- I have a problem with the exit function declaration in
Selon RENNUIT Antoine 203220 Thésard [EMAIL PROTECTED]:
That works better, but I still have several errors :
- what is fadmin project useful for? The true question is can I
remove it, because it needs FLTK, and it's a painful task to install it
correctly (no .lib, no .dll...).
fgadmin
discussions
Objet : RE: [Flightgear-devel] MSVC
It was my fault.
The solution in FlightGear/cvs/FlightGear/FlightGear-2.sln is supposed to
compile all you need for FlightGear.
You just have to get software in the structure below :
FlightGear/cvs/FlightGear = FlightGear
FlightGear/cvs/SimGear
RENNUIT Antoine 203220 Thésard a écrit :
Hello,
- you put flightgear, simgear, and plib sources into a cvs
directory; so I guess we have to use the newest cvs version (I used tarball
cvs version) of these packages. When I put the cvs version of flightGear
sources in the project, VC tells
RENNUIT Antoine 203220 Thésard wrote:
Hello,
I am new to flight gear. I am looking for a how to to compile FG under
MSVC (either 6 or .net) : at the moment I am completely lost in all the
libraries needed to link : how come these libraries (simgear, plib, zlib,
metakit, openAL...) do not broadcast
Quoting Erik Hofman :
RENNUIT Antoine 203220 Thésard wrote:
Hello,
I am new to flight gear. I am looking for a how to to compile FG under
MSVC (either 6 or .net) : at the moment I am completely lost in all the
libraries needed to link : how come these libraries (simgear, plib, zlib,
I cannot download the new file...
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de Frederic
Bouvier
Envoyé : vendredi 3 décembre 2004 14:54
À : FlightGear developers discussions
Objet : Re: [Flightgear-devel] MSVC
Quoting Erik Hofman :
RENNUIT Antoine
Now it works, sorry for disturbing...
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de RENNUIT
Antoine 203220 Thésard
Envoyé : vendredi 3 décembre 2004 14:59
À : 'FlightGear developers discussions'
Objet : RE: [Flightgear-devel] MSVC
I cannot download
PROTECTED] la part de RENNUIT
Antoine 203220 Thésard
Envoyé : vendredi 3 décembre 2004 14:59
À : 'FlightGear developers discussions'
Objet : RE: [Flightgear-devel] MSVC
I cannot download the new file...
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] la part de
Frederic Bouvier [EMAIL PROTECTED] wrote:
I am receiving an increasing number of request for working
project files for MSVC. While I can't reply specifically
to everybody, I packed my current, unedited, project files
here :
ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/
I'm proud to
massimo casanova wrote:
hello, Frederic
I'm trying to compile FG under MSVC7 but I've almost the same problems I
found on MSVC6
problems with templates and typedefs.
I use
FlightGear-0.9.3
SimGear-0.3.4
plib-1.6.0.tar
can you tell me what
- compiler version (any patch?) do you use
-
Jonathan Adam Muse wrote:
Hello Everyone,
I'm an aerospace engineering student looking to use flightgear as an
image generator for my generic flight dynamics model project. I'm
starting to get decent at programming but some of these flightgear
errors are above me. Is there anyone out
For those who may care, I fixed the MacOS problems. It turns out that
the OpenGL Extension that FlightGear are referencing have ARB
extensions rather than EXT. I.e.,
glPointParameterfvEXT
glPointParameterfEXT
becomes
glPointParameterfvARB
glPointParameterfARB
Jonathan Polley
Here is the
- Original Message -
From: Jonathan Polley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, January 02, 2003 9:13 PM
Subject: Re: [Flightgear-devel] MSVC Build Problems in src/Main/main.cxx
For those who may care, I fixed the MacOS problems. It turns out that
the OpenGL
Jonathan Polley writes:
The latest updat to src/Main/main.cxx is generating the following errors for MSVC
6.0 (and I assume for all Windows compilers).
c:\fgdev\flightgear\src\main\main.cxx(749) : error C2065:
'GL_DISTANCE_ATTENUATION_EXT' : undeclared identifier
I just noticed that the problem also exists for MacOS 10.2(.3), which I
believe is at least OpenGL 1.3 (and 10.2.3 is OpenGL 1.4). Any ideas
as to what is missing?
Thanks,
Jonathan Polley
On Wednesday, January 1, 2003, at 10:25 AM, Norman Vine wrote:
Jonathan Polley writes:
The latest
From: Curtis L. Olson [EMAIL PROTECTED]
Jonathan Polley writes:
MSVC does not have fmin() defined, so complains in vacuum.cxx.
gcc-2.95 is also complaining about it missing.
Same for MSVC 7.
Cheers,
-Fred
___
Flightgear-devel mailing list
On Tue, 24 Sep 2002 03:46:54 -0400
Norman Vine [EMAIL PROTECTED] wrote:
Bernie Bright writes:
On Mon, 23 Sep 2002 18:51:25 -0700
Jonathan Polley [EMAIL PROTECTED] wrote:
MSVC does not have fmin() defined, so complains in vacuum.cxx.
gcc 2.95.3 complains too. fmin() is only
Bernie Bright writes:
Well, as far as I can tell, fmin() is C99 not Std C++. We could
use std::min() but that causes a problem with MSVC where you have
to use cpp_min() instead. And so it goes on...
My fault -- I didn't realize that fmin() was non-ANSI. I've fixed it
in the CVS (in
Jonathan Polley writes:
MSVC does not have fmin() defined, so complains in vacuum.cxx.
gcc-2.95 is also complaining about it missing.
Curt.
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED]
Minnesota
> I have submitted a patch to David. Here is what is needed :
>
> SG_USING_STD(find);
> SG_USING_STD(vectorSGPropertyChangeListener *>);
> SG_USING_STD(vectorSGPropertyNode *>);
>
> around line 29 of props.cxx
>
> -Fred
I just entered the changes and everything builds just fine. I'll wait for
I haven't tried building this, but this sort of error looks like you just
have to put a
using namespace std;
into the props.cxx
Cheers, Christian
At 07:50 PM 20/06/2002 -0500, you wrote:
I just updated to the latest CVS for SimGear and tried to build. While Mac
OS X builds like a champ,
I didn't see anything like that in the new files, but I may not know what,
exactly, I should be looking for. The only new using clause was in
props.cxx:
using std::find;
Jonathan Polley
On Thursday, June 20, 2002, at 08:02 PM, Christian Stock wrote:
I haven't tried building this, but
I have submitted a patch to David. Here is what is needed :
SG_USING_STD(find);
SG_USING_STD(vectorSGPropertyChangeListener *);
SG_USING_STD(vectorSGPropertyNode *);
around line 29 of props.cxx
-Fred
- Original Message -
From: Jonathan Polley [EMAIL PROTECTED]
I didn't see anything
To avoid this problem in future, maybe we should define a macro in
simgear/compiler.h. Something like:
#ifdef SG_NO_INCLASS_MEMBER_INITIALIZATION
# define SG_STATIC_CONSTANT(type, assignment) enum { assignment }
#else
# define SG_STATIC_CONSTANT(type, assignment) static const type
assignment
These
items should not be limited, anyhow. Where is this done???
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jonathan
PolleySent: Monday, April 08, 2002 9:24 PMTo:
[EMAIL PROTECTED]Subject: [Flightgear-devel] MSVC
Still not
This is in a section of code that is shipping the data over the net,
so in this case a fixed limited structure size is desirable. We can
always extend it later if we need to ... re: David's/Andy's principle
of not over designing to much too early (aka doing just barely enough
to get by?) :-)
Jonathan Polley
writes:
Although SimGear is now building under MSVC (thanks).MSVC also does not like having
constants defined in a class (net_fdm.hxx and raw_ctrls.hxx).static
const int FG_MAX_ENGINES = 4;static const int FG_MAX_WHEELS = 3;static
const int FG_MAX_TANKS = 2;When I
On Sunday, April 7, 2002, at 10:47 AM, Frederic Bouvier wrote:
From: Jonathan Polley [EMAIL PROTECTED]
Just updated to the newest CVS for everything. While linux us now
compiling and running just fine (thanks Curt), MSVC continues to whine.
First: The #include fg_props.hxx in viewer.cxx
- Original Message -
From: Jonathan Polley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, April 07, 2002 6:45 PM
Subject: Re: [Flightgear-devel] MSVC Yada Yada Yada
On Sunday, April 7, 2002, at 10:47 AM, Frederic Bouvier wrote:
From: Jonathan Polley [EMAIL PROTECTED]
Just
On Sat, 2002-04-06 at 17:53, Jonathan Polley wrote:
Just updated to the newest CVS for everything. While linux us now
compiling and running just fine (thanks Curt), MSVC continues to whine.
First: The #include fg_props.hxx in viewer.cxx needs to be #include
fg_props.hxx
Second: I am
On Saturday, April 6, 2002, at 08:09 PM, Tony Peden wrote:
On Sat, 2002-04-06 at 17:53, Jonathan Polley wrote:
p.s. Another odd thing happened. It seems that, in the latest update of
FGAerodynamics, when
inline double GetForces(int n) const {return vForces(n);}
was changed to
double
56 matches
Mail list logo
