Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd)
Another question please? Is it correct to have a floder called src under C:\FGDev\fg-fatimais-flightgear under C:\FGDev\fg-fatimais-flightgear\build? Maybe why I have a fatal error when I try to compile FlightGear.sln under C:\FGDev\fg-fatimais-flightgear\build ... Many thanks, Cheers, Fatima -Message d'origine- De : ThorstenB [mailto:bre...@gmail.com] Envoyé : jeudi 1 décembre 2011 20:16 À : Iervolino Fatima Cc : FlightGear developers discussions Objet : Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd) Am 01.12.2011 15:53, schrieb Iervolino Fatima: Hi Thorsten, I've rebuilt all successfully. But I'm still have the same problem as before: What I can do to solve it? First of all, are you really using CMake to configure your FlightGear build (not just for OSG!) - or are you maybe using the MSVC project which is (still) located in the FlightGear folder below project/VC90 ? The latter is unmaintained now - since we switched to CMake a few days ago (see our email topic :) ). I have no idea what happens if you compiled with the now-obsolete MSVC project file. @James/Frederic: Could we drop the VC90 project file now? It's confusing if that's still around. No one is checking this file now, and it's impossible to know what people are using as long as it's still around. Fatima, if you have used cmake for FlightGear (not just for OSG), then check the generated file src/Include/config.h from your FlightGear (build) directory. It should contain: #define ENABLE_YASIM #define ENABLE_JSBSIM = If these were missing (or commented out), then this explains your problem. You could add/enable these defines manually to have a quick success with building. But better also fix the root cause, otherwise issues will be back later. Also check the CMakeCache.txt file (not sure if that has the same name for Windows). It should contain: //Set to ON to build FlightGear with JSBSim FDM ENABLE_JSBSIM:BOOL=ON //Set to ON to build FlightGear with YASIM FDM ENABLE_YASIM:BOOL=ON If these switches are set to OFF (or even missing), then the CMake configuration step hasn't worked for FlightGear. If you can't fix the issue, then please attach the src/Include/config.h and CMakeCache.txt files to your email, so we can see how your build is configured. And remember, these files should be _generated_ on your machine (whenever you run cmake) - so check their file date/time to see if they are really fresh. It may also be a good idea to see if you maybe have any other (old) config.h in one of your include directories - so that the compiler somehow finds the wrong file first... cheers, Thorsten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd)
Hi, Yes, I agree with you. I di dit and the built is now completely successful. Thanks, Cheers, Fatima -Message d'origine- De : ThorstenB [mailto:bre...@gmail.com] Envoyé : mercredi 30 novembre 2011 21:14 À : Iervolino Fatima Cc : FlightGear developers discussions Objet : Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd) Am 30.11.2011 15:40, schrieb Iervolino Fatima: I get systematically the same error: 1Compilation en cours... 1ReaderWriterOGR.cpp 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(41) : error C2146: erreur de syntaxe : absence de ';' avant l'identificateur 'CPLOSGErrorHandler' 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(41) : error C2182: 'CPL_STDCALL' : utilisation non conforme du type 'void' 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(43) : error C4430: spécificateur de type manquant - int est pris en compte par défaut. Remarque : C++ ne prend pas en charge int par défaut 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(50) : warning C4508: 'CPLOSGErrorHandler' : la fonction doit retourner une valeur ; type de retour 'void' pris par défaut 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(100) : error C2664: 'CPLSetErrorHandler' : impossible de convertir le paramètre 1 de 'int (__cdecl *)(CPLErr,int,const char *)' en 'CPLErrorHandler' 1 Aucune fonction ayant ce nom dans la portée ne correspond au type de la cible 1Le journal de génération a été enregistré à l'emplacement file://c:\FGDev\OpenSceneGraph-3.0.1\OpenSceneGraph\build\src\osgPlugins\ogr\osgdb_ogr.dir\Debug\BuildLog.htm 1Plugins ogr - 4 erreur(s), 1 avertissement(s Have you an idea how to solve it? Many thanks, Hmm. Unfortunately I have little help here. Actually you're compiling a part of the OpenSceneGraph library there - not FlightGear itself. However, I can see that for some reason the OSG plugin ogr was never compiled on my system. Not sure what it does, but it seems we don't need this for FlightGear. Maybe this OSG plugin is broken somehow. I would probably just try to disable ogr (i.e. remove the ADD_SUBDIRECTORY(ogr) from the CMakeList.txt) and see if that works. Otherwise you may need to ask the OpenSceneGraph forum/devel-list. cheers, Thorsten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd)
Hi Thorsten, I've rebuilt all successfully. But I'm still have the same problem as before: What I can do to solve it? Thanks, Fatima -Message d'origine- De : ThorstenB [mailto:bre...@gmail.com] Envoyé : mercredi 30 novembre 2011 21:14 À : Iervolino Fatima Cc : FlightGear developers discussions Objet : Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd) Am 30.11.2011 15:40, schrieb Iervolino Fatima: I get systematically the same error: 1Compilation en cours... 1ReaderWriterOGR.cpp 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(41) : error C2146: erreur de syntaxe : absence de ';' avant l'identificateur 'CPLOSGErrorHandler' 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(41) : error C2182: 'CPL_STDCALL' : utilisation non conforme du type 'void' 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(43) : error C4430: spécificateur de type manquant - int est pris en compte par défaut. Remarque : C++ ne prend pas en charge int par défaut 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(50) : warning C4508: 'CPLOSGErrorHandler' : la fonction doit retourner une valeur ; type de retour 'void' pris par défaut 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(100) : error C2664: 'CPLSetErrorHandler' : impossible de convertir le paramètre 1 de 'int (__cdecl *)(CPLErr,int,const char *)' en 'CPLErrorHandler' 1 Aucune fonction ayant ce nom dans la portée ne correspond au type de la cible 1Le journal de génération a été enregistré à l'emplacement file://c:\FGDev\OpenSceneGraph-3.0.1\OpenSceneGraph\build\src\osgPlugins\ogr\osgdb_ogr.dir\Debug\BuildLog.htm 1Plugins ogr - 4 erreur(s), 1 avertissement(s Have you an idea how to solve it? Many thanks, Hmm. Unfortunately I have little help here. Actually you're compiling a part of the OpenSceneGraph library there - not FlightGear itself. However, I can see that for some reason the OSG plugin ogr was never compiled on my system. Not sure what it does, but it seems we don't need this for FlightGear. Maybe this OSG plugin is broken somehow. I would probably just try to disable ogr (i.e. remove the ADD_SUBDIRECTORY(ogr) from the CMakeList.txt) and see if that works. Otherwise you may need to ask the OpenSceneGraph forum/devel-list. cheers, Thorsten image001.png-- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd)
Hi Thorsten, Thanks for your reply. I've decided to repeat again the full process for compiling FG under Windows. I get systematically the same error: 1Compilation en cours... 1ReaderWriterOGR.cpp 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(41) : error C2146: erreur de syntaxe : absence de ';' avant l'identificateur 'CPLOSGErrorHandler' 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(41) : error C2182: 'CPL_STDCALL' : utilisation non conforme du type 'void' 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(43) : error C4430: spécificateur de type manquant - int est pris en compte par défaut. Remarque : C++ ne prend pas en charge int par défaut 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(50) : warning C4508: 'CPLOSGErrorHandler' : la fonction doit retourner une valeur ; type de retour 'void' pris par défaut 1..\..\..\..\src\osgPlugins\ogr\ReaderWriterOGR.cpp(100) : error C2664: 'CPLSetErrorHandler' : impossible de convertir le paramètre 1 de 'int (__cdecl *)(CPLErr,int,const char *)' en 'CPLErrorHandler' 1Aucune fonction ayant ce nom dans la portée ne correspond au type de la cible 1Le journal de génération a été enregistré à l'emplacement file://c:\FGDev\OpenSceneGraph-3.0.1\OpenSceneGraph\build\src\osgPlugins\ogr\osgdb_ogr.dir\Debug\BuildLog.htm 1Plugins ogr - 4 erreur(s), 1 avertissement(s Have you an idea how to solve it? Many thanks, Cheers, Fatima -Message d'origine- De : ThorstenB [mailto:bre...@gmail.com] Envoyé : mardi 29 novembre 2011 14:43 À : Iervolino Fatima Cc : FlightGear developers discussions Objet : Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd) Hi Fatima, that's not an aircraft-dependent problem - you seem to have a fundamental issue with loading the scenery itself. May well be related to the PNG lib / malformed chunk warnings in your console - this could be scenery textures which fail to load. Maybe check which PNG library you're using - and if the files in the data directory are ok. You can also try to add this to your fgfs command-line: --prop:sim/sceneryloaded-override=1 That won't fix the underlying issue, but it will tear down the splash screen immediately instead of waiting for scenery to be loaded. Looking at the scenery may help seeing what the issue is - i.e. do you get any scenery at all, are only (some) textures missing etc. cheers, Thorsten Am 29.11.2011 13:49, schrieb Iervolino Fatima: Hello Thorsten, Many thanks for your help. It's better now but the FlightGear is blocked to the step of loading scenery for all kind of aircrafts. Could you please help me? You'll find here https://docs.google.com/document/d/1Sw7OM3piEq-TUhHnIRTcKw3lpQT2QUrdApcYYPX8KdM/edit a screenshot of the program the command DOS. Cheers, Fatima -Message d'origine- De : ThorstenB [mailto:bre...@gmail.com] Envoyé : lundi 28 novembre 2011 17:26 À : FlightGear developers discussions Cc : Iervolino Fatima Objet : Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd) Am 28.11.2011 16:57, schrieb Alan Teeder: This was sent directly to me. Does anyone know what her problem is likely to be? (I, and others , have already given several answers to this question on the FG forum) After having compiling in DEBUG RELEASE mode FlightGear under Windows, I get systematically an error while I'm trying to launch fgfs under Windows command DOS. “Fatal error: Unrecognized flight model 'jsb', cannot init flight dynamics model.” Alan, please add a forum link when cross posting: http://www.flightgear.org/forums/viewtopic.php?f=35t=14371hilit=jsb With the introduction of CMake it is possible to enable/disable the different FDMs. The JSBSim and YASim are enabled by default, only the LARCSim and UIUC flight dynamics are excluded from the build by default. As Anders said on the forum, something must have gone wrong while configuring the build, so somehow the default was changed, and JSBSim support disabled and excluded from the build. Either remove CMakeCache.txt and run cmake again (so the correct defaults are taken), or run cmake -DENABLE_JSBSIM:BOOL=ON to override the current local setting. cheers, Thorsten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd)
Hello Thorsten, Many thanks for your help. It's better now but the FlightGear is blocked to the step of loading scenery for all kind of aircrafts. Could you please help me? You'll find here https://docs.google.com/document/d/1Sw7OM3piEq-TUhHnIRTcKw3lpQT2QUrdApcYYPX8KdM/edit a screenshot of the program the command DOS. Cheers, Fatima -Message d'origine- De : ThorstenB [mailto:bre...@gmail.com] Envoyé : lundi 28 novembre 2011 17:26 À : FlightGear developers discussions Cc : Iervolino Fatima Objet : Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd) Am 28.11.2011 16:57, schrieb Alan Teeder: This was sent directly to me. Does anyone know what her problem is likely to be? (I, and others , have already given several answers to this question on the FG forum) After having compiling in DEBUG RELEASE mode FlightGear under Windows, I get systematically an error while I'm trying to launch fgfs under Windows command DOS. “Fatal error: Unrecognized flight model 'jsb', cannot init flight dynamics model.” Alan, please add a forum link when cross posting: http://www.flightgear.org/forums/viewtopic.php?f=35t=14371hilit=jsb With the introduction of CMake it is possible to enable/disable the different FDMs. The JSBSim and YASim are enabled by default, only the LARCSim and UIUC flight dynamics are excluded from the build by default. As Anders said on the forum, something must have gone wrong while configuring the build, so somehow the default was changed, and JSBSim support disabled and excluded from the build. Either remove CMakeCache.txt and run cmake again (so the correct defaults are taken), or run cmake -DENABLE_JSBSIM:BOOL=ON to override the current local setting. cheers, Thorsten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
