Hi Andreas,
On 11 Sep 2011, at 12:18, Andreas Gaeb wrote: > one problem I noticed with that is that the headers aren't added to the > project in SimGear. At least Codeblocks is not able to add them automatically > parsing the includes, so the attached patch does that explicitly. This allows > things like "jump to definition" also for header-only classes, which up to > now produces errors. Apart from that, I'm doing fairly well with the > generated CB projects. Haven't tried kdevelop, though. Thanks for sharing your experiences. After having played with the new kdevelop, my first impression is leaning toward the positive side, but not completely positive. I like the enhanced editing, and online syntax checking. Particularly, the context sensitve list of suggested completions is really handy. But, some other options, like the kdevelop definition of a current project selection is slightly awkward, and I also found that the integrated cmake is slightly awkward when you choose a build location other than the default. But, given that I have been learning as I went, it's probable that I left a trail of garbage behind. So, I might restart from scratch and take it from there. > > While we're at it, FindOpenSceneGraph.cmake claims it was added in CMake > 2.6.3, while SimGear's CMakeList only has cmake_minimum_required(VERSION 2.6) > , so this should be updated (maybe directly to 2.8?). I thought that Fred mentioned on the mailing list the we only officially support cmake 2.8.0 and higher. > > Yet another thing: when trying to build with CMAKE_BUILD_TYPE RelWithDebInfo > or MinSizeRel, the FlightGear build will fail unless you have SimGear > libraries in Release configuration still around (against which it will link, > but not against the matching configuration). This is because > SelectLibraryConfigurations.cmake only knows about Debug and Release. Fixing > this might however be a bit tricky, and I don't know how many people are > actually going to use these build types. Maybe a warning about an unsupported > build type is sufficient. As a fallback it is always possible to alter > CMAKE_CXX_FLAGS directly. > Which actually brings me to the next question: I'm currently trying to build a heavily optimized version of FlightGear, and want to pass a number of options cmake. I got the basic mechanism to work; i.e. -D CMAKE_CXX_FLAGS="-O3 -Wall". But, in my autoconf based compile script, I pass an option containing an equals character (i.e. "="_). When I try to pass that to cmake, using for example: -D CMAKE_CXX_FLAGS="-O3 -Wall -march=native", if found that the entire token containing the = character, as well as all the tokens following it, are ignored. I've tried most of the known unix tricks to escape the = character, but to no avail. Any ideas? Cheers, Durk ------------------------------------------------------------------------------ Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
