On Tue 2009-03-03 09:20, kent williams wrote: > Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and > lets you generate your build files.
This and the fact that most modules aren't written to handle multiple passes (for instance, if the wrong version is found on the first pass, the cache becomes corrupt) means that I frequently configure cmake packages by repeatedly running $ rm -rf * && cmake .. -DVAR1=foo -DVAR2=bar and adding options based on the output. This is silly, but it's definitely the most robust solution and in my experience saves time. Writing robust Find* modules is hard work and there are many issues [*] to overcome before we can even give standard advice to make the hack above unnecessary. Your specific issue sounds like it's just a bug, but very similar issues are deeper and I find ccmake/cmake-gui to be brittle as soon as anything unexpected happens. [*] many mentioned at http://www.cmake.org/Wiki/CMake:Improving_Find*_Modules Jed
pgpiTyIFq3M24.pgp
Description: PGP signature
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
