В Чтв, 16/04/2009 в 13:58 +0200, Andreas Pakulat пишет: > On 16.04.09 07:31:54, Michael Jackson wrote: > > Basically what this boils down to is there may need to be a new generator > > for QtCreator. This would require cooperation between the QtCreator team > > and the developers creating that generator so that everything that is > > needed is put into the generator. This will end up being kind of a boot > > strapping process at first but in the end I think would be well worth it > > for both CMake and QtCreator. > > Another option that can be considered is simply parsing and interpreting > the CMakeLists.txt files in QtCreator. Of course that would be a lot easier > if CMake would provide some of its internals as API in a library, as > currently one has to check the source of CMake to find out how the > functions are implemented. > > This approach is what we've done for KDvelop4 and it works quite well (even > though we don't yet support all things that the CMake api offers).
I guess we could just use internal CMake headers and link to CMakeLib. As cmake binaries do. But this approach misses flexibility of separate CMake upgrades (CMakeLib is a static library), I don't think it is worth to use CMakeLib unless it will become a shared library. Sergey _______________________________________________ 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
