There is a fault somewhere in Flightgear/Simgear cmake which makes this happen from time to time.
Here is a quick fix. Step 12a If you get the error Could NOT find SimGear (missing: SIMGEAR_VERSION_OK) (Required is at least version "2.5.0") Press "Add Entry" In the window that comes up set Name to SIMGEAR_VERSION_OK, Type to BOOL and tick the Value box. Press "OK" and continue. This bypasses the broken Simgear version check. Alan -----Original Message----- From: Rob Dosogne Sent: Tuesday, October 18, 2011 10:06 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Cmake (soon) Thanks for the instructions, Alan. I tried this twice from scratch—SimGear configures & builds just fine, but CMake gets stuck trying to configure FlightGear. I set CMAKE_INSTALL_PREFIX as you said, and building "INSTALL" seems to have copied SimGear into that directory, but CMake can't find it; any ideas? #### Git revision is 3rdparty files located in C:/FlightGear apr-1-config not found, implement manual search for APR Could NOT find LIBSVN (missing: LIBSVN_LIBRARIES LIBSVN_INCLUDE_DIR) C:/FlightGear/3rdParty.x64/include adding runtime JS dependencies C:/FlightGear/install/include looking for version: 2.5.0 CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:91 (MESSAGE): Could NOT find SimGear (missing: SIMGEAR_VERSION_OK) (Required is at least version "2.5.0") Call Stack (most recent call first): C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:252 (_FPHSA_FAILURE_MESSAGE) CMakeModules/FindSimGear.cmake:217 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) CMakeLists.txt:179 (find_package) Configuring incomplete, errors occurred! #### cheers, Rob On Tue, Oct 18, 2011 at 09:41, Alan Teeder <ajtee...@v-twin.org.uk> wrote: > It is about time that such a document was started, many thanks. > > However windows users will most likely use the CMake gui, which hides all > that geeky command line stuff. > > For Cmake gui the following seems to work. > > 1. Set up a work directory as described in > http://wiki.flightgear.org/index.php/Building_Flightgear_-_Windows. > (NOTE: this is now out of date as the 3rdparty , zlib and OSG are all > ready > to use at ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/ ) > > 2. Open the Cmake gui > > 3. Set “Where is the source code” and “Where to build the binaries” to > C:/Flightgear/simgear” (or wherever you have put simgear) > > 4. Press the “Configure” button. The first time that the project is > generated, Cmake will bring up a window asking which compiler you wish to > use. Normally just accept Cmakes suggestion, and press Finish. Cmake will > now do a check on your system and will produce a preliminary build > configuration.´ > > 5. Check for errors in the red window. Cmake should have found OSG, zlib > and > your 3rdparty directories. > > 6. Set CMAKE_INSTALL_PREFIX to C:/Flightgear/install. This is probably not > necessary for Windows XP, but is required for Windows 7 as the default > (C:\Program Files) is protected. > > 7. Press “Configure” once more. Errors should all have gone. > > 8. Press “Generate”. Cmake will now write a windows sln and project files > in the simgear directory. > > 9. Open C:\Flightgear\simgear\simgear.sln. MSVC should come up. Select > Release (or debug if you need it) build and then build-all. > > 10. Once simgear has built successfully (there will be some warnings), > build > the INSTALL project. This will copy the simgear libraries and include > files > to C:flightgear\install. > > 11. Now repeat the Cmake process for flightgear. The directories to > choose > are C:/Flightgear/flightgear. > > 12. It is important to chose the same CMAKE_INSTALL_PREFIX, otherwise the > simgear libraries will not be found. > > 13. Open C:\Flightgear\flightgear\flightgear.sln. As with simgear, build > all, and then build INSTALL. > > 14. Flightgear and other executables should be in > C:\Flightgear\install\bin. > > No doubt I have left something out, but this does describe the basic > process. > > Alan > From: James Turner > Sent: Tuesday, October 18, 2011 9:40 AM > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] Cmake (soon) > _ > > On 17 Oct 2011, at 18:38, Curtis Olson wrote: > > Would it be possible to write a quick "howto" for doing some basic > coding/developer things in cmake. Like: "how to add a new source file to > the project." Or "how to add a new module/library to the project". > Maybe > a few quick summeries of "how to install in a custom directory", how to > build with custom compiler options, how to configure for debug vs. release > build, or some the more subtle build options that invoke different levels > of > optimizations or warnings. > > > I've written this up, at least a first attempt, will commit it later > today, > and people can review it for sanity / correctness / omissions :) > > Either that, or our cmake experts need to be willing and ready to respond > to > frustrated "dumb" questions in a timely manner -- and do that over time if > we don't have central place to find this information without investing the > required time to become cmake experts ourselves. > > > I'm assuming that's true regardless :) > > James > > ________________________________ > ------------------------------------------------------------------------------ > 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. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > > ________________________________ > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > ------------------------------------------------------------------------------ > 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. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- Rob ------------------------------------------------------------------------------ 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. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------------ 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. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel