[Flightgear-devel] Changes to SimGear required?
I've just been trying to compile a current CVS update of both SimGear and FlightGear. Simegear builds properly, but FlightGear falls over in src/Main with: fg_init.cxx: In function `bool fgInitSubsystems()': fg_init.cxx:1046: no matching function for call to `SkySceneLoader::Load (string, double, double)' /usr/local/include/simgear/sky/clouds3d/SkySceneLoader.hpp:51: candidates are: bool SkySceneLoader::Load(SGPath) Which version of SimGear should FlightGear-cvs currently build against? -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Changes to SimGear required?
This definitely looks like a version mismatch between simgear/flightgear. Make sure you've build the latest simgear-cvs and then check all the dumb stuff, like you installed it, you don't have extra older versions of simgear floating around your hard drive, etc. etc. Regards, Curt. Jon Stockill writes: I've just been trying to compile a current CVS update of both SimGear and FlightGear. Simegear builds properly, but FlightGear falls over in src/Main with: fg_init.cxx: In function `bool fgInitSubsystems()': fg_init.cxx:1046: no matching function for call to `SkySceneLoader::Load (string, double, double)' /usr/local/include/simgear/sky/clouds3d/SkySceneLoader.hpp:51: candidates are: bool SkySceneLoader::Load(SGPath) Which version of SimGear should FlightGear-cvs currently build against? -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- 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] Changes in SimGear
Curtis L. Olson wrote: Christian Mayer writes: Hi, is there a reason why SimGear/misc/zfstram.hxx was changed from #ifdef HAVE_ZLIB # include zlib.h #else # include simgear/zlib/zlib.h #endif to #include zlib.h It was a slight phylisophical shift. Although zlib and metakit aren't standard on all systems, they are standard on many systems, and there were various problems trying to build them inside of the simgear make system. Well, standard on most *nix systems. But not Windos (but probably not Cygwin) Anyway, could all #include zlib.h lines be changed back to #ifdef HAVE_ZLIB # include zlib.h #else # include simgear/zlib/zlib.h #endif w/o causing any trouble? This would help me. I wouldn't need any other change as the directories are still there. CU, Christian -- The idea is to die young as late as possible.-- Ashley Montague Whoever that is/was; (c) by Douglas Adams would have been better... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Changes in SimGear
Christian Mayer wrote: Anyway, could all #include zlib.h lines be changed back to #ifdef HAVE_ZLIB # include zlib.h #else # include simgear/zlib/zlib.h #endif w/o causing any trouble? This would help me. I wouldn't need any other change as the directories are still there. You have to realize that metakit and zlib aren't compiled in SimGear anymore. Adding thise lines may also add some confusion. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Changes in SimGear
Erik Hofman wrote: Christian Mayer wrote: Anyway, could all #include zlib.h lines be changed back to #ifdef HAVE_ZLIB # include zlib.h #else # include simgear/zlib/zlib.h #endif w/o causing any trouble? This would help me. I wouldn't need any other change as the directories are still there. You have to realize that metakit and zlib aren't compiled in SimGear anymore. Adding thise lines may also add some confusion. You are right about the standard make process. But as MSVC doesn't have zlib (I didn't have problems with metakit but that should be theoretically the same problem) I have to compile it with SimGear. I wouldn't care if it's changed to #ifndef HAVE_NO_ZLIB but just a plain zlib.h doesn't work for me (w/o much hazle). CU, Christian -- The idea is to die young as late as possible.-- Ashley Montague Whoever that is/was; (c) by Douglas Adams would have been better... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Changes in SimGear
Hi, is there a reason why SimGear/misc/zfstram.hxx was changed from #ifdef HAVE_ZLIB # include zlib.h #else # include simgear/zlib/zlib.h #endif to #include zlib.h ? As ZLIB isn't standard (perhaps except on Linux) it's great to have the fallback to the supplied version. And adding the additional include directories to ZLIB and probably Metakit (dunno as my compilation stopped that early) isn't my idea of a clean compilation. CU, Christian -- The idea is to die young as late as possible.-- Ashley Montague Whoever that is/was; (c) by Douglas Adams would have been better... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Changes in SimGear
Christian Mayer wrote: Hi, is there a reason why SimGear/misc/zfstram.hxx was changed from #ifdef HAVE_ZLIB # include zlib.h #else # include simgear/zlib/zlib.h #endif to #include zlib.h Apart from fixing all occurances of the single #include zlib.h FGFS complied staight away under MSVC!! (If I'd have a Champange bottle I'd open it). But there are still the old runtime problems :( (JSBsim #NAN and LaRCsim won't let me start the engine) CU, Christian -- The idea is to die young as late as possible.-- Ashley Montague Whoever that is/was; (c) by Douglas Adams would have been better... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Changes in SimGear
Christian Mayer writes: Hi, is there a reason why SimGear/misc/zfstram.hxx was changed from #ifdef HAVE_ZLIB # include zlib.h #else # include simgear/zlib/zlib.h #endif to #include zlib.h ? As ZLIB isn't standard (perhaps except on Linux) it's great to have the fallback to the supplied version. And adding the additional include directories to ZLIB and probably Metakit (dunno as my compilation stopped that early) isn't my idea of a clean compilation. It was a slight phylisophical shift. Although zlib and metakit aren't standard on all systems, they are standard on many systems, and there were various problems trying to build them inside of the simgear make system. So, I ripped out the zlib and metakit trees from the distribution so they are never built by default as part of simgear, and instead include zlib-1.1.3.tar.gz and metakit-2.4.2-32.tar.gz as a convenience for those that do need to build these packages themselves. But, because they are configured and compiled separately, simgear builder can better follow their specific install instructions and won't have the problem with simgear inadvertantly screwing things up on some platforms. Regards, Curt. -- Curtis Olson Intelligent Vehicles Lab 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
