| Re: [cdt-dev] Introduction |
Hello Doug,
The CMake support we have is very early. I don¹t think it¹s even in the build artifacts yet. But I am looking to CMake as a great way to support multi-platform builds just as qmake does,
currently, I cannot make out of what use the CMake support in eclipse is. When creating a new CMake project and trying to build it, all I get is an error message "Build not configured correctly".
We might have a difference of strategy though. My thoughts were to have CMake projects as single projects rooted at the directory you point cmake at meaning it could contain many executables and libraries in a single project. Combined with EGit¹s newer support for submodules, it just feels like a more natural way to work. And it¹s something we¹ve been doing at QNX for a while with BSP projects which contain multiple drivers (which are executables with QNX¹s microkernel architecture) and libraries and such.
my "strategy" would be to support anything you can do with CMake. Otherwise, its not CMake support IMO. My ideal would be to somehow adapt the CMake object model to the eclipse-internal object model, as CLion seems to be doing it. QtCreator also handles CMake seamlessly. I wouldn't want to go through some json file that is output by CMake, but rather directly access their classes.
I also think that the apporach both take in terms of UI is fair: let the user edit the CMake file, monitor changes and reload it once (s)he is done.
Chris