Re: [Flightgear-devel] MSVC build error
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 you in advance. Start ouput Linking... LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs; use /NODEFAULTLIB:library Don't use that option. Be sure you compiled all programs and libraries with the same 'Code Generation' options. /MT is fine if it is everywhere. You didn't use this sentence. See below. Thanks a lot for your suggestion. It helped and I managed to get rid of some of the linking errors. But I'm still stuck with another 74 errors I hope you will be able to help me locate and fixed. I've noticed the errors revolve around the gz function, the sgsoundmanager (which to me looks like an maybe an openal error??)... If you could take a quick look at the error output and point me in the right direction. Thank you very much. Start output Linking... LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification LIBCMTD.lib(dbgheap.obj) : error LNK2005: _malloc already defined in LIBCMT.lib(malloc.obj) It is clearly stated here that there is a conflict between C runtimes. LIBCMTD is used when 'Code Generation' C/C++ option is set to 'Debug Multithread (/MTd)' while LIBCMT is from 'Multithread (/MT)'. There is a suggestion to use /NODEFAULTLIB:library link option but it is a no-go and build unusable programs. You should have to hunt where you put /MTd and replace it to /MT because using a Debug version of FlightGear is the right way to have very poor framerate. new_gui.obj : error LNK2001: unresolved external symbol class puFont FONT_SANS_12B (?FONT_SANS_12B@@3VpuFont@@A) This symbol comes from PLIB's fnt.lib library. main.obj : error LNK2019: unresolved external symbol __imp__alListenerf referenced in function public: void __thiscall SGSoundMgr::set_volume(float) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) Should come from OpenAL. SimGear.lib(zfstream.obj) : error LNK2019: unresolved external symbol _gzopen referenced in function public: class gzfilebuf * __thiscall gzfilebuf::open(char const *,int) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]@Z) Comes from zlib.lib. There is a source tarball in SimGear/src-libs/ SimGear.lib(code.obj) : error LNK2019: unresolved external symbol _naUnlock referenced in function _naNewContext This is Nasal code in SimGear .\Debug/FlightGear.exe : fatal error LNK1120: 40 unresolved externals So, to summarize : 1. clear your Code Generation conflict issues 2. add fnt.lib to the solution, 3. add openal to the solution, 4. add zlib.lib to the solution, 5. add nasal files to the SimGear project 6. fly :) -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs; use /NODEFAULTLIB:library Don't use that option. Be sure you compiled all programs and libraries with the same 'Code Generation' options. /MT is fine if it is everywhere. .\Debug/FlightGear.exe : fatal error LNK1120: 119 unresolved externals You have to add all the files containing the unresolved symbols in you solution in order to compile and link them to fgfs.exe For exemple, in the line : environment.obj : error LNK2019: unresolved external symbol public: bool __thiscall SGEnviro::get_turbulence_enable_state(void)const ([EMAIL PROTECTED]@@QBE_NXZ) referenced in function public: virtual double __thiscall FGEnvironment::get_turbulence_magnitude_norm(void)const ([EMAIL PROTECTED]@@UBENXZ) it is said that the SGEnviro class ( the name before :: ) is missing. A quick search in the source tree tells me that it is in simgear/environment/visual_enviro.cxx that has to be added in the simgear project file. Do that until you have no unresolved external. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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 advance. Start ouput Linking... LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs; use /NODEFAULTLIB:library Don't use that option. Be sure you compiled all programs and libraries with the same 'Code Generation' options. /MT is fine if it is everywhere. .\Debug/FlightGear.exe : fatal error LNK1120: 119 unresolved externals You have to add all the files containing the unresolved symbols in you solution in order to compile and link them to fgfs.exe For exemple, in the line : environment.obj : error LNK2019: unresolved external symbol public: bool __thiscall SGEnviro::get_turbulence_enable_state(void)const ([EMAIL PROTECTED]@@QBE_NXZ) referenced in function public: virtual double __thiscall FGEnvironment::get_turbulence_magnitude_norm(void)const ([EMAIL PROTECTED]@@UBENXZ) it is said that the SGEnviro class ( the name before :: ) is missing. A quick search in the source tree tells me that it is in simgear/environment/visual_enviro.cxx that has to be added in the simgear project file. Do that until you have no unresolved external. -Fred Hi Fred, Thanks a lot for your suggestion. It helped and I managed to get rid of some of the linking errors. But I'm still stuck with another 74 errors I hope you will be able to help me locate and fixed. I've noticed the errors revolve around the gz function, the sgsoundmanager (which to me looks like an maybe an openal error??)... If you could take a quick look at the error output and point me in the right direction. Thank you very much. Start output Linking... LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification LIBCMTD.lib(dbgheap.obj) : error LNK2005: _malloc already defined in LIBCMT.lib(malloc.obj) LIBCMTD.lib(dbgheap.obj) : error LNK2005: __nh_malloc already defined in LIBCMT.lib(malloc.obj) LIBCMTD.lib(dbgheap.obj) : error LNK2005: __heap_alloc already defined in LIBCMT.lib(malloc.obj) LIBCMTD.lib(dbgheap.obj) : error LNK2005: _calloc already defined in LIBCMT.lib(calloc.obj) LIBCMTD.lib(dbgheap.obj) : error LNK2005: _realloc already defined in LIBCMT.lib(realloc.obj) LIBCMTD.lib(dbgheap.obj) : error LNK2005: _free already defined in LIBCMT.lib(free.obj) LIBCMTD.lib(dbgheap.obj) : error LNK2005: __msize already defined in LIBCMT.lib(msize.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: __get_sbh_threshold already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: __set_sbh_threshold already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_heap_init already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_find_block already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_free_block already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_alloc_block already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_alloc_new_region already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_alloc_new_group already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_resize_block already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_heapmin already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(sbheap.obj) : error LNK2005: ___sbh_heap_check already defined in LIBCMT.lib(sbheap.obj) LIBCMTD.lib(isctype.obj) : error LNK2005: __isctype already defined in LIBCMT.lib(isctype.obj) LIBCMTD.lib(isctype.obj) : error LNK2005: ___isctype_mt already defined in LIBCMT.lib(isctype.obj) LINK : warning LNK4098: defaultlib 'LIBCMTD' conflicts with use of other libs; use /NODEFAULTLIB:library new_gui.obj : error LNK2001: unresolved external symbol class puFont FONT_SANS_12B (?FONT_SANS_12B@@3VpuFont@@A) new_gui.obj : error LNK2001: unresolved external symbol class puFont FONT_HELVETICA_14 (?FONT_HELVETICA_14@@3VpuFont@@A) main.obj : error LNK2019: unresolved external symbol __imp__alListenerf referenced in function public: void __thiscall SGSoundMgr::set_volume(float) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) fg_fx.obj : error LNK2001: unresolved external symbol __imp__alListenerf SimGear.lib(soundmgr_openal.obj) : error LNK2001: unresolved external symbol __imp__alListenerf main.obj : error LNK2019: unresolved external symbol __imp__alListenerfv referenced in function public: void __thiscall SGSoundMgr::set_listener_pos(float *) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2001: unresolved
Re: [Flightgear-devel] MSVC build error
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 '/INCREMENTAL:NO' specification LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs; use /NODEFAULTLIB:library environment.obj : error LNK2019: unresolved external symbol public: double __thiscall SGEnviro::get_cloud_turbulence(void)const ([EMAIL PROTECTED]@@QBENXZ) referenced in function public: virtual double __thiscall FGEnvironment::get_turbulence_magnitude_norm(void)const ([EMAIL PROTECTED]@@UBENXZ) environment.obj : error LNK2019: unresolved external symbol public: bool __thiscall SGEnviro::get_turbulence_enable_state(void)const ([EMAIL PROTECTED]@@QBE_NXZ) referenced in function public: virtual double __thiscall FGEnvironment::get_turbulence_magnitude_norm(void)const ([EMAIL PROTECTED]@@UBENXZ) environment_mgr.obj : error LNK2001: unresolved external symbol public: bool __thiscall SGEnviro::get_turbulence_enable_state(void)const ([EMAIL PROTECTED]@@QBE_NXZ) environment.obj : error LNK2001: unresolved external symbol class SGEnviro sgEnviro (?sgEnviro@@3VSGEnviro@@A) environment_mgr.obj : error LNK2001: unresolved external symbol class SGEnviro sgEnviro (?sgEnviro@@3VSGEnviro@@A) renderer.obj : error LNK2001: unresolved external symbol class SGEnviro sgEnviro (?sgEnviro@@3VSGEnviro@@A) environment_mgr.obj : error LNK2019: unresolved external symbol public: __thiscall FGClouds::FGClouds(class FGEnvironmentCtrl *) (??0FGClouds@@[EMAIL PROTECTED]@@@Z) referenced in function public: __thiscall FGEnvironmentMgr::FGEnvironmentMgr(void) (??0FGEnvironmentMgr@@[EMAIL PROTECTED]) environment_mgr.obj : error LNK2019: unresolved external symbol public: __thiscall FGClouds::~FGClouds(void) (??1FGClouds@@[EMAIL PROTECTED]) referenced in function public: void * __thiscall FGClouds::`scalar deleting destructor'(unsigned int) (??_GFGClouds@@[EMAIL PROTECTED]) environment_mgr.obj : error LNK2019: unresolved external symbol public: void __thiscall SGEnviro::set_turbulence_enable_state(bool) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: bool __thiscall SGEnviro::get_lightning_enable_state(void)const ([EMAIL PROTECTED]@@QBE_NXZ) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: void __thiscall SGEnviro::set_lightning_enable_state(bool) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: int __thiscall FGClouds::get_update_event(void)const ([EMAIL PROTECTED]@@QBEHXZ) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: void __thiscall FGClouds::set_update_event(int) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: bool __thiscall SGEnviro::get_precipitation_enable_state(void)const ([EMAIL PROTECTED]@@QBE_NXZ) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: void __thiscall SGEnviro::set_precipitation_enable_state(bool) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: int __thiscall SGEnviro::get_CacheResolution(void)const ([EMAIL PROTECTED]@@QBEHXZ) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: void __thiscall SGEnviro::set_CacheResolution(int) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: int __thiscall SGEnviro::get_clouds_CacheSize(void)const ([EMAIL PROTECTED]@@QBEHXZ) referenced in function public: virtual void __thiscall FGEnvironmentMgr::bind(void) ([EMAIL PROTECTED]@@UAEXXZ) environment_mgr.obj : error LNK2019: unresolved external symbol public: void __thiscall SGEnviro::set_clouds_CacheSize(int)
Re: [Flightgear-devel] MSVC problems with 0.9.8 tarball
--- 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 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 __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC problems with 0.9.8 tarball
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 always see water if there's no scenery installed for your start location. Patrick isn't seeing _anything_ other than the hud and menus AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC problems with 0.9.8 tarball
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 started the sim with: FlightGear.exe --fg-root=C:\fgfs\fgfs-base-0.9.8\data --aircraft=c172p Pretty standard I'd think. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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 http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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 mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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 FlightGear (or a relatively recent snapshot) with an older SimGear. Andy Thinking about it, I did download flightgear source and simgear source from the 'bleeding edge' link from the website. But when compiling that simgear, I ran into an error... it couldn't find any files in the scene\sky\clouds3d directory. So instead I downloaded the 0.3.8 version. Could that be a problem? Thanks. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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 problem? These words, the same thing say. :) Yes, always match your FlightGear and SimGear versions. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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 downloaded the 0.3.8 version. Could that be a problem? These words, the same thing say. :) Yes, always match your FlightGear and SimGear versions. 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. Thanks. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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 have, perhaps it's an old snapshot. The CVS logs show that all the files in the clouds3d directory were removed on June 25th. It's an old implementation. Really, if you want to use real bleeding edge stuff, then you want to be checking the files out of CVS directly. Cygwin contains a command line cvs client that will work with the directions you find on the website. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC build error
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 probably _cdecl (/Gd). You'll probably want to make sure all subprojects share that setting, and you'll probably want to do a clean build of everything after the change. Hope this helps. It didn't take me long to get past the problemjust some experimenting with the project settings (under properties). As for the moonpos.cxx, that problem also sounds familiar. Try adding it back in to the project in the appropriate place (probably the same place you found it). Seems like MSVC was initially confused about that for some reason, and the fix was that simple. Jim A -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of bass pumped Sent: Monday, September 05, 2005 6:35 PM To: FlightGear developers discussions Subject: [Flightgear-devel] MSVC build error Hi all, 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. Is there anyway I can debug this? I also had a problem where it said it couldn't find the moonpos.cxx file. I deleted that file from the solution, but I'm not sure if I'll run into problems when it starts linking flightgear. Any help would be great! Thank you. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC build error
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 setting, and you'll probably want to do a clean build of everything after the change. ... Jim A ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC build error
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. 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 FlightGear (or a relatively recent snapshot) with an older SimGear. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
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 error - glut32.lib I am trying to compile FG on MSVC.net (7.0) on a Windows platform. I have been sucessful through plib, simgear and now FG is providing me with a fatal LNK error 1104: cannot open file 'glut32.lib' . The 'glut32.lib' file exists in the C:\windows\system32 folder... Can anyone suggest a solution or path to examine. Mike ___ The glut32.lib should be put in the %VCInstallDir%\lib directory. For instance, I have MSVC.net 2003, and it is in the C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib folder. Make sure it is in that folder and then recompile. Hopefully, everything will compile and link correctly. chuck ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC error - glut32.lib
In MSVC.net (not 2003) the correct location for the library is the %VCInstallDir%\PlatformSDK\lib directory. Steven P. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chuck Cole Sent: Tuesday, July 05, 2005 4:17 PM To: 'FlightGear developers discussions' 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 error - glut32.lib I am trying to compile FG on MSVC.net (7.0) on a Windows platform. I have been sucessful through plib, simgear and now FG is providing me with a fatal LNK error 1104: cannot open file 'glut32.lib' . The 'glut32.lib' file exists in the C:\windows\system32 folder... Can anyone suggest a solution or path to examine. Mike ___ The glut32.lib should be put in the %VCInstallDir%\lib directory. For instance, I have MSVC.net 2003, and it is in the C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\lib folder. Make sure it is in that folder and then recompile. Hopefully, everything will compile and link correctly. chuck ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC 7.1 Runtime Error
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
airport=KSFO aircraft=A-10cl disable-sound and I get the
following runtime error almost immediately:
Debug assertion failed!
Program: fgfs.exe
File: isctype.c
Line: 68
Expression: (unsigned)(c+1) = 256
Has anyone ever encountered this error? Is it possible to set
breakpoints in Flightgear and debug it that way?
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
You can debug, no problem.
The assert is a known problem, it happens with a debug build under VS,
you have to change a view lines in simgear, patch attached.
Harald.
Index: strutils.cxx
===
RCS file: /var/cvs/SimGear-0.3/source/simgear/misc/strutils.cxx,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 strutils.cxx
--- strutils.cxx7 Sep 2002 02:58:19 - 1.1.1.1
+++ strutils.cxx26 Apr 2005 17:01:34 -
@@ -41,14 +41,14 @@
while (i len)
{
- while (i len isspace(str[i]))
+ while (i len isspace((unsigned char)str[i]))
{
++i;
}
j = i;
- while (i len !isspace(str[i]))
+ while (i len !isspace((unsigned char)str[i]))
{
++i;
}
@@ -57,7 +57,7 @@
{
result.push_back( str.substr(j, i-j) );
++countsplit;
- while (i len isspace(str[i]))
+ while (i len isspace((unsigned char)str[i]))
{
++i;
}
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC 7.1 Runtime Error
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 fg-root=c:\\GS_PTT\\Flightgear\\data airport=KSFO aircraft=A-10cl disable-sound and I get the following runtime error almost immediately: Debug assertion failed! Program: fgfs.exe File: isctype.c Line: 68 Expression: (unsigned)(c+1) = 256 Has anyone ever encountered this error? Is it possible to set breakpoints in Flightgear and debug it that way? You can debug, no problem. The assert is a known problem, it happens with a debug build under VS, you have to change a view lines in simgear, patch attached. BTW: you will get a 2x to 3x framerate improvement if you compile flightgear in release mode, and you will not be annoyed by this assertion failure. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC 7.1 Runtime Error
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 be causing this? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC 7.1 Runtime Error
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 start. What could be causing this? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d 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. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC 7.1 Runtime Error
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 just wasn't echoing the information to the command window so I thought it was stuck. Thanks for your help. Ben. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC
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 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 is a utility project and can be removed - I have a problem with the exit function declaration in stdlib.h, it tells me it is a redefinition, any idea? edit glut.h, locate exit and then change the file to have : #if _MSC_VER = 1200 _CRTIMP __declspec(noreturn) void __cdecl exit(int); #else _CRTIMP void __cdecl exit(int); #endif instead of : _CRTIMP void __cdecl exit(int); that works only for MSVC 6 -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC
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 stdlib.h, it tells me it is a redefinition, any idea? Thanks, Antoine. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC
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 is a utility project and can be removed - I have a problem with the exit function declaration in stdlib.h, it tells me it is a redefinition, any idea? edit glut.h, locate exit and then change the file to have : #if _MSC_VER = 1200 _CRTIMP __declspec(noreturn) void __cdecl exit(int); #else _CRTIMP void __cdecl exit(int); #endif instead of : _CRTIMP void __cdecl exit(int); that works only for MSVC 6 -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC
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 me it cannot find dme.cxx, navcom.cxx, and radiostack.cxx. Actually these files are not in the cvs version of flightGear, but they are in the 0.9.6 version of the sources : what must I do? Delete the files from the project? Add dme.cxx, navcom.cxx, and radiostack.cxx, and there associated .hxx to my cvs files? - you added the following directory D:\Flight gear\FG-ProjectFiles-msvc71\FlightGear\cvs\plib\examples\src\ssg\majik. The project under VC tells me there should be 3 files called elevation_map.h, image_map.h, and magik_demo.cxx in this directory, unfortunately, you did not deliver them within the project files, do you know what's the problem? - I have the same problem with tux_example.cxx - the file jpegfactory.hxx needs to include jpeglib.h, and jerror.h, I cannot find anything about these files... I had a look on the web, I think it comes from a library, could you tell me more about that? How should it be installed to be used with FG project? Wow, that makes a lot of questions. I hope I am not too boring... Antoine. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Frederic Bouvier Envoyé : vendredi 3 décembre 2004 16:10 À : FlightGear developers 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= SimGear FlightGear/cvs/plib = plib FlightGear/zlib-1.1.4 = zlib pthread-snap-2004-06-22 = pthread for win32 The zip file reflect this structure. -Fred Quoting RENNUIT Antoine 203220 Thésard : 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 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 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 with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. You can find MSVC (7.0) project files here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I've just made an update today with current project files for .NET 2003. Obviouly, path have to be changed. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC
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 me it cannot find dme.cxx, navcom.cxx, and radiostack.cxx. Actually these files are not in the cvs version of flightGear, but they are in the 0.9.6 version of the sources : what must I do? Delete the files from the project? Add dme.cxx, navcom.cxx, and radiostack.cxx, and there associated .hxx to my cvs files? - you added the following directory D:\Flight gear\FG-ProjectFiles-msvc71\FlightGear\cvs\plib\examples\src\ssg\majik. The project under VC tells me there should be 3 files called elevation_map.h, image_map.h, and magik_demo.cxx in this directory, unfortunately, you did not deliver them within the project files, do you know what's the problem? - I have the same problem with tux_example.cxx - the file jpegfactory.hxx needs to include jpeglib.h, and jerror.h, I cannot find anything about these files... I had a look on the web, I think it comes from a library, could you tell me more about that? How should it be installed to be used with FG project? Wow, that makes a lot of questions. I hope I am not too boring... Antoine. MSVC projects are not updated by core developers, so they are always lagging. You should consider CVS is the reference and delete instances in the project when files are deleted from CVS and add new ones that appears from time to time. You should remove the projects you don't want. tux_example, majik_demo and fgrun are additionnal programs that are not needed by flightgear. You should fine a copy of libjpeg ( search freshmeat ) for MSVC to compile jpegfactory.cxx, otherwise, remove that file because it is optionnally compiled under linux. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC
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 with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. You can find MSVC (7.0) project files here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC
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, metakit, openAL...) do not broadcast with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. You can find MSVC (7.0) project files here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I've just made an update today with current project files for .NET 2003. Obviouly, path have to be changed. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC
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 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 with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. You can find MSVC (7.0) project files here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I've just made an update today with current project files for .NET 2003. Obviouly, path have to be changed. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] MSVC
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 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 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 with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. You can find MSVC (7.0) project files here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I've just made an update today with current project files for .NET 2003. Obviouly, path have to be changed. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
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= SimGear FlightGear/cvs/plib = plib FlightGear/zlib-1.1.4 = zlib pthread-snap-2004-06-22 = pthread for win32 The zip file reflect this structure. -Fred Quoting RENNUIT Antoine 203220 Thésard : 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 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 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 with simple .lib files??? I read several threads from the forum, but did not find enough information to go on. You can find MSVC (7.0) project files here: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ I've just made an update today with current project files for .NET 2003. Obviouly, path have to be changed. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC project files
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 see that you make ongoing use of this ftp-server ;-) 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] MSVC Build Problems
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 - FG version (FG+Simgear+plib) have you compiled I've, moreover, problems to configure a correct build project for Simgear, since in 0.3.4 there's no MSVC project. You can get a .dsp file here : http://cvs.simgear.org/cgi-bin/viewcvs/viewcvs.cgi/*checkout*/SimGear/SimGear.dsp?rev=1.5cvsroot=SimGear-0.3 ( Curt, what happened to the MSVC files in the SimGear distributions ? they disappeared ) I use MSVC .Net v 7.0.9466 and compile PLIB, SG and FG from CVS. The project file was originally the one provided in the distribution but now heavily modified to follow CVS development and to match some build requirement of FLTK or CGAL. Otherwise, if you can tell what are your current problems ( copy of error messages ), we could help you more precisely. -Fred PS: If people posting on FG list could avoid posting HTML, it would be easier to format replies ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Build Problems
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 there that can explain how
to fix this microsoft vc error? I'm using MSVC 6.0.
MSVC 6 is not able to compile FG CVS without a lot of ugly patches
because it is buggy with templates, even with Service Packs.
I use MSVC 7 with success and recommend to do so if possible.
I am not submitting patches for it anymore.
Just ignore the warnings. You can add
#ifdef _MSC_VER
#pragma warning( disable: 4786 )
#endif
at the top of the file if you want
For the errors, apply the patch below, and be prepared to do several
things like that in other directories.
-Fred
D:\fgfs-msvc6\source\src\GUIcvs -z3 diff -u
cvs server: Diffing .
Index: menubar.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/GUI/menubar.cxx,v
retrieving revision 1.15
diff -u -r1.15 menubar.cxx
--- menubar.cxx 22 May 2003 08:42:38 - 1.15
+++ menubar.cxx 19 Oct 2003 08:49:47 -
@@ -229,7 +229,7 @@
// Delete all those bindings
SG_LOG(SG_GENERAL, SG_INFO, Deleting bindings);
-mapstring,vectorFGBinding * ::iterator it;
+FGBinding_vector_map::iterator it;
it = _bindings.begin();
for (it = _bindings.begin(); it != _bindings.end(); it++) {
SG_LOG(SG_GENERAL, SG_INFO, Deleting bindings for it-first);
Index: menubar.hxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/GUI/menubar.hxx,v
retrieving revision 1.6
diff -u -r1.6 menubar.hxx
--- menubar.hxx 21 Jan 2003 15:44:21 - 1.6
+++ menubar.hxx 19 Oct 2003 08:49:47 -
@@ -22,6 +22,8 @@
class puObject;
class FGBinding;
+typedef mapstring,vectorFGBinding * FGBinding_vector_map;
+
/**
* XML-configured PUI menu bar.
@@ -100,7 +102,7 @@
puMenuBar * _menuBar;
// A map of bindings for the menubar.
-mapstring,vectorFGBinding * _bindings;
+FGBinding_vector_map _bindings;
// These are hoops that we have to jump through because PUI doesn't
// do memory management for lists. We have to allocate the arrays,
Index: new_gui.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/GUI/new_gui.cxx,v
retrieving revision 1.18
diff -u -r1.18 new_gui.cxx
--- new_gui.cxx 24 Sep 2003 17:20:56 - 1.18
+++ new_gui.cxx 19 Oct 2003 08:49:47 -
@@ -135,7 +135,7 @@
delete _menubar;
_menubar = 0;
-mapstring,SGPropertyNode *::iterator it;
+PropertyNode_map::iterator it;
for (it = _dialog_props.begin(); it != _dialog_props.end(); it++)
delete it-second;
_dialog_props.clear();
Index: new_gui.hxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/GUI/new_gui.hxx,v
retrieving revision 1.15
diff -u -r1.15 new_gui.hxx
--- new_gui.hxx 24 Sep 2003 17:20:56 - 1.15
+++ new_gui.hxx 19 Oct 2003 08:49:47 -
@@ -25,6 +25,7 @@
class FGDialog;
class FGBinding;
+typedef mapstring,SGPropertyNode * PropertyNode_map;
/**
* XML-configured GUI subsystem.
@@ -151,7 +152,7 @@
FGMenuBar * _menubar;
FGDialog * _active_dialog;
-mapstring,SGPropertyNode * _dialog_props;
+PropertyNode_map _dialog_props;
};
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
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 Extension that FlightGear are referencing have ARB extensions rather than EXT. I.e., glPointParameterfvEXT glPointParameterfEXT becomes glPointParameterfvARB glPointParameterfARB Jonathan Polley Here is the CVS diff. Index: main.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/main.cxx,v retrieving revision 1.53 diff -r1.53 main.cxx 53a54,58 #if defined (__APPLE__) #define GL_SGIS_point_parameters 1 #include OpenGL/glext.h #endif 748a754,757 #if defined (__APPLE__) glPointParameterfvARB(GL_DISTANCE_ATTENUATION_EXT, quadratic); glPointParameterfARB(GL_POINT_SIZE_MIN_EXT, 1.0); #else 750c759,760 glPointParameterfEXT(GL_POINT_SIZE_MIN_EXT, 1.0); --- glPointParameterfEXT(GL_POINT_SIZE_MIN_EXT, 1.0); #endif 792a803,806 #if defined (__APPLE__) glPointParameterfvARB(GL_DISTANCE_ATTENUATION_EXT, default_attenuation); #else 794a809 #endif ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Build Problems in src/Main/main.cxx
- 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 Extension that FlightGear are referencing have ARB extensions rather than EXT. I.e., glPointParameterfvEXT glPointParameterfEXT becomes glPointParameterfvARB glPointParameterfARB Jonathan Polley Here is the CVS diff. Index: main.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/main.cxx,v retrieving revision 1.53 diff -r1.53 main.cxx 53a54,58 #if defined (__APPLE__) #define GL_SGIS_point_parameters 1 #include OpenGL/glext.h #endif 748a754,757 #if defined (__APPLE__) glPointParameterfvARB(GL_DISTANCE_ATTENUATION_EXT, quadratic); glPointParameterfARB(GL_POINT_SIZE_MIN_EXT, 1.0); #else 750c759,760 glPointParameterfEXT(GL_POINT_SIZE_MIN_EXT, 1.0); --- glPointParameterfEXT(GL_POINT_SIZE_MIN_EXT, 1.0); #endif 792a803,806 #if defined (__APPLE__) glPointParameterfvARB(GL_DISTANCE_ATTENUATION_EXT, default_attenuation); #else 794a809 #endif ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Build Problems in src/Main/main.cxx
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 c:\fgdev\flightgear\src\main\main.cxx(750) : error C2065: 'GL_POINT_SIZE_MIN_EXT' : undeclared identifier AFAIK these are post OpenGL version 1.1 hence not supported by the M$oft headers and require including the equivalant of extgl.h or just defining them ourselves #ifndef GL_EXT_point_parameters #define GL_EXT_point_parameters 1 #define GL_POINT_SIZE_MIN_EXT 0x8126 #define GL_POINT_SIZE_MAX_EXT 0x8127 #define GL_POINT_FADE_THRESHOLD_SIZE_EXT0x8128 #define GL_DISTANCE_ATTENUATION_EXT 0x8129 typedef void (APIENTRY * glPointParameterfEXTPROC) (GLenum pname, GLfloat param); typedef void (APIENTRY * glPointParameterfvEXTPROC) (GLenum pname, const GLfloat *params); extern glPointParameterfEXTPROC glPointParameterfEXT; extern glPointParameterfvEXTPROC glPointParameterfvEXT; #endif /* GL_EXT_point_parameters */ HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Build Problems in src/Main/main.cxx
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 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 c:\fgdev\flightgear\src\main\main.cxx(750) : error C2065: 'GL_POINT_SIZE_MIN_EXT' : undeclared identifier AFAIK these are post OpenGL version 1.1 hence not supported by the M$oft headers and require including the equivalant of extgl.h or just defining them ourselves #ifndef GL_EXT_point_parameters #define GL_EXT_point_parameters 1 #define GL_POINT_SIZE_MIN_EXT 0x8126 #define GL_POINT_SIZE_MAX_EXT 0x8127 #define GL_POINT_FADE_THRESHOLD_SIZE_EXT0x8128 #define GL_DISTANCE_ATTENUATION_EXT 0x8129 typedef void (APIENTRY * glPointParameterfEXTPROC) (GLenum pname, GLfloat param); typedef void (APIENTRY * glPointParameterfvEXTPROC) (GLenum pname, const GLfloat *params); extern glPointParameterfEXTPROC glPointParameterfEXT; extern glPointParameterfvEXTPROC glPointParameterfvEXT; #endif /* GL_EXT_point_parameters */ HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC 6.0 Problem with systems/vacuum/vacuum.cxx
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 [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC 6.0 Problem with systems/vacuum/vacuum.cxx
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 defined if _ISOC99_SOURCE is defined before including math.h. I wonder if we are going to need a sg_math.h if so here is a first stab at one [cut] 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... Bernie ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC 6.0 Problem with systems/vacuum/vacuum.cxx
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 advance of integration of Alex's vacuum model from steam.cxx). 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] MSVC 6.0 Problem with systems/vacuum/vacuum.cxx
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 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] MSVC Build Problem for props.cxx
> 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 the patch to get submitted to CVS to make the changes permanent. Thanks for the changes, Jonathan Polley
Re: [Flightgear-devel] MSVC Build Problem for props.cxx
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, MSVC is complaining (again). If I backup two versions of the file, I can get it to build (but I get link errors with FlightGear). The compilation errors I get are as follows (looks like another STL problem?). props.cxx c:\simgear\simgear\misc\props.cxx(1997) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'iterator' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1997) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'it' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1998) : error C2065: 'find' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1999) : error C2446: '!=' : no conversion from 'class SGPropertyChangeListener ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(1999) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyChangeListener ** ' c:\simgear\simgear\misc\props.cxx(2299) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2299) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2300) : error C2440: '=' : cannot convert from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' c:\simgear\simgear\misc\props.cxx(2301) : error C2100: illegal indirection c:\simgear\simgear\misc\props.cxx(2301) : error C2227: left of '-removeChangeListener' must point to class/struct/union c:\simgear\simgear\misc\props.cxx(2333) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2333) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2335) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2335) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' Jonathan Polley /blockquote/x-html ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Build Problem for props.cxx
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 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, MSVC is complaining (again). If I backup two versions of the file, I can get it to build (but I get link errors with FlightGear). The compilation errors I get are as follows (looks like another STL problem?). props.cxx c:\simgear\simgear\misc\props.cxx(1997) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'iterator' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1997) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(1997) : error C2065: 'it' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1998) : error C2065: 'find' : undeclared identifier c:\simgear\simgear\misc\props.cxx(1999) : error C2446: '!=' : no conversion from 'class SGPropertyChangeListener ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(1999) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyChangeListener ** ' c:\simgear\simgear\misc\props.cxx(2299) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2299) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2300) : error C2440: '=' : cannot convert from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2300) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' c:\simgear\simgear\misc\props.cxx(2301) : error C2100: illegal indirection c:\simgear\simgear\misc\props.cxx(2301) : error C2227: left of '-removeChangeListener' must point to class/struct/union c:\simgear\simgear\misc\props.cxx(2333) : error C2653: 'vector ' : is not a class or namespace name c:\simgear\simgear\misc\props.cxx(2333) : error C2146: syntax error : missing ';' before identifier 'it' c:\simgear\simgear\misc\props.cxx(2335) : error C2446: '!=' : no conversion from 'class SGPropertyNode ** ' to 'int' This conversion requires a reinterpret_cast, a C-style cast or function-style cast c:\simgear\simgear\misc\props.cxx(2335) : error C2040: '!=' : 'int' differs in levels of indirection from 'class SGPropertyNode ** ' Jonathan Polley /blockquote/x-html ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Build Problem for props.cxx
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 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: ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Still not Building
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
#endif
Usage then becomes:
class Foo {
SG_STATIC_CONSTANT(int, FG_MAX_ENGINES = 4);
...
}
which expands to either
static const int FG_MAX_ENGINES = 4;
or
enum { FG_MAX_ENGINES = 4; };
I think the problem with Norman's solution is that you can't use the
value later in the class declaration, as an array size for example.
Cheers,
Bernie
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] MSVC Still not Building
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 BuildingAlthough 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
used the recommended, and I apologize for not remembering by whom, change
toenum {FG_MAX_TANKS = 2,FG_MAX_WHEELS = 3,FG_MAX_ENGINES =
4,};it compiles, links, and runs just
fine.Thanks!Jonathan PolleyFlying
Again!
smime.p7s
Description: application/pkcs7-signature
RE: [Flightgear-devel] MSVC Still not Building
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?) :-)
Curt.
Jon Berndt writes:
These items should not be limited, anyhow. Where is this done???
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jonathan Polley
Sent: Monday, April 08, 2002 9:24 PM
To: [EMAIL PROTECTED]
Subject: [Flightgear-devel] MSVC Still not Building
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 used the recommended, and I apologize for not remembering by
whom, change to
enum {FG_MAX_TANKS = 2,
FG_MAX_WHEELS = 3,
FG_MAX_ENGINES = 4,
};
it compiles, links, and runs just fine.
Thanks!
Jonathan Polley
Flying Again!
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
HTMLHEAD
META http-equiv=Content-Type content=text/html; charset=us-ascii
META content=MSHTML 6.00.2713.1100 name=GENERATOR/HEAD
BODY
DIVSPAN class=742563802-09042002FONT face=Arial color=#ff size=2These
items should not be limited, anyhow. Where is this done???/FONT/SPAN/DIV
BLOCKQUOTE
style=PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #ff 2px solid
DIV class=OutlookMessageHeader dir=ltr align=leftFONT face=Tahoma
size=2-Original Message-BRBFrom:/B
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]BOn Behalf Of /BJonathan
PolleyBRBSent:/B Monday, April 08, 2002 9:24 PMBRBTo:/B
[EMAIL PROTECTED]BRBSubject:/B [Flightgear-devel] MSVC
Still not BuildingBRBR/FONT/DIVAlthough SimGear is now building under
MSVC (thanks).BRBR?fontfamily?param CourierMSVC also does not like
having constants defined in a class (net_fdm.hxx and
raw_ctrls.hxx).BRBRstatic const int FG_MAX_ENGINES = 4;BRstatic const
int FG_MAX_WHEELS = 3;BRstatic const int FG_MAX_TANKS = 2;BRBRWhen I
used the recommended, and I apologize for not remembering by whom, change
toBRBRenum {FG_MAX_TANKS = 2,BRFG_MAX_WHEELS = 3,BRFG_MAX_ENGINES =
4,BR};BRBRit compiles, links, and runs just
fine.BRBRThanks!BRBRJonathan PolleyBRBRFlying
Again!BR/BLOCKQUOTE?/fontfamily/BODY/HTML
--
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] MSVC Still not Building
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 used the recommended, and I
apologize for not remembering by whom, change toenum {FG_MAX_TANKS =
2,FG_MAX_WHEELS = 3,FG_MAX_ENGINES = 4,};it compiles,
links, and runs just fine.
Ibelievethat all that is needed is to declare the
variables
outside of the class declarationwith file scpe
ie in
the header -- foo.hxx
class
foo {
static
const int a:
}
and
theninthe C file - foo.cxx - somthing likethis should
work
const
int foo::a = 5;
Norman
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 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 NO. It needs #include Main/fg_props.hxx like every other files that includes fg_props.hxx But viewer.cxx is in Main already. It just seems odd that it add a path to a header that is in its own directory. Jonathan Polley ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Yada Yada Yada
- 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 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 NO. It needs #include Main/fg_props.hxx like every other files that includes fg_props.hxx But viewer.cxx is in Main already. It just seems odd that it add a path to a header that is in its own directory. If you compile flightgear, you already have an include path to FlightGearSrcRoot/src so adding Main/fg_props.hxx ( or Main/fg_props.hxx ) is just doing here like any other place in FG where fg_props.hxx is included. Special case always create troubles ! Cheers, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Yada Yada Yada
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 getting the following error when building SimGear
props.cxx
C:\SimGear\simgear\misc\props.cxx(1920) : error C2665: 'delete' : none of
the 2 overloads can convert parameter 1 from type 'const char *'
C:\SimGear\simgear\misc\props.cxx(1949) : error C2248: 'entry' : cannot
access public class declared in class 'SGPropertyNode::hash_table'
C:\SimGear\simgear\misc\props.hxx(1124) : see declaration of
'entry'
C:\SimGear\simgear\misc\props.cxx(1949) : error C2248: 'entry' : cannot
access public class declared in class 'SGPropertyNode::hash_table'
C:\SimGear\simgear\misc\props.hxx(1124) : see declaration of
'entry'
C:\SimGear\simgear\misc\props.cxx(1950) : error C2248: 'entry' : cannot
access public class declared in class 'SGPropertyNode::hash_table'
C:\SimGear\simgear\misc\props.hxx(1124) : see declaration of
'entry'
As usual, it is having problems with overloading, and my C++ skills are
non-existent in this area.
While FlightGear proper compiles just fine, it complains at link time:
FGOutput.obj : error LNK2001: unresolved external symbol public: double
__thiscall FGFCS::GetThrottlePos(int) (?GetThrottlePos@FGFCS@@QAENH@Z)
FGTrimAxis.obj : error LNK2001: unresolved external symbol public: double
__thiscall FGFCS::GetThrottleCmd(int) (?GetThrottleCmd@FGFCS@@QAENH@Z)
I have looked and the only thing I see that is different about these two
routines, from what I am use to seeing, is that they are 'const.' They
are both public so I am not sure why MSVC is not putting them in the
global symbol table.
double GetThrottleCmd(int engine) const;
Removing the 'const' causes problems to crop up elsewhere.
I can't offer anything here.
Thanks,
Jonathan Polley
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 GetForces(int n) const {return vForces(n);}
that MSVC no longer has a problem with the overloading of GetForces() (i.e.
, I could abandon my local changes). Any ideas on that one?
I don't know, but discussion here seems to indicate that specifying
inline is pointless anyway since we take a pointer to it.
So we'll take it!
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
--
Tony Peden
[EMAIL PROTECTED]
We all know Linux is great ... it does infinite loops in 5 seconds.
-- attributed to Linus Torvalds
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] MSVC Yada Yada Yada
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 GetForces(int n) const {return vForces(n);}
that MSVC no longer has a problem with the overloading of GetForces() (i.
e.
, I could abandon my local changes). Any ideas on that one?
I don't know, but discussion here seems to indicate that specifying
inline is pointless anyway since we take a pointer to it.
So we'll take it!
I just tried removing the 'inline' from the front of the methods that MSVC
complains about and it appears that FGAerodynamics is the only place that
stopped complaining. Go figure.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
