16.02.2012, 04:06, "Pau Garcia i Quiles" <[email protected]>:
> On Wed, Feb 15, 2012 at 10:05 AM, Campbell Barton <[email protected]> > wrote: >> Im not sure what there is to be gained here. > Adding/removing files directly from Qt Creator (yes, that is important for > many developers), creating modules ("finders") directly in Qt Creator, > integration with the simulators, cross-compilation chains, etc I'd say there > is a lot to be gained. >> CMake is a language - it executes, and poops out a project file. >> As a qtcreator/cmake user Im happy for qtcreator not to be *smart* >>> about cmake, infact I'd prefer it be kept that way. >> All qtcreator needs to do is load that project file correctly, which, >> I should add - it currently does not do (it misses includes and >> defines from CMake), IMHO this should be first priority to get >> working. > Avoiding the project generation altogether would be even better. Irrelevance of any intermediate product is beyond question for me; one may argue that hand-crafted parser (like in KDevelop) is better, but use of CMakeLib seems to be more reliable (Qt Creator will see actual project model of CMake instead of "guessed" one), and will provide additional capabilities like changing of project configuration from GUI without use of external tools. -- Regards, Konstantin _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
