On Tuesday 01 November 2011, craig.sc...@csiro.au wrote: ... > If you do that, you create a circular dependency, since CMake requires Qt > to build its GUI application. Yes, you could build CMake's command line > tools only, then Qt, then build CMake's GUI app, or alternatively you > could install some previously built CMake package before building Qt, but > these are steps that should not be necessary.
I don't think that's a problem. CMake has the same issue itself, you need cmake to build cmake. So, what you do is you can either bootstrap cmake (then first a stripped down version of cmake is built, which then builds the full cmake), or use an older version of cmake to build the new cmake. The same could be done here. Use cmake and cmake-gui built against Qt x.y to build Qt x.y+1. If there is no Qt at all, cmake-gui will not be built, it is optional. Alex -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
