I do not find it to be a joke, rather than being one of the best out there (if not THE best).
I tried CLion just 2 weeks ago. It was a nice experience when it came to CMake, but it’s C++ IntelliSense capabilities seem to be lacking. (Truth be told, I did try with the experimental MSVC support, so I do plan to revisit CLion once that is baked.) The thing I did not like about CLion is that it tries to cater the click-click way of getting a build ready, but does not go all the way (nor even half the way). I tried getting a build ready of one „src/Main.cpp” and a „inc/Header.hpp” (I believe this is the most common source file organization), but I failed to add the „target_include_directories” statement through the UI. So, if CLion caters those who wish to add source files through the UI, which even prompts for a CMake variable to add the source file to, and even follows along the lines of changing the CMake script when one relocates files through the UI… then why can’t I set something as simple as an include directory through the UI??? I believe the problem CLion got caught in is that it is very hard (if not impossible) to wrap a UI around a stateful, imperative language with also letting the user edit the CMakeLists.txt file. VS had a much easier job with MSBuild (an XML-based build system), but with CMake, it’s much harder. This was one of the reasons I suggested roughly a year ago to create an IR for CMake (to decouple generators from the front-end, and also facilitate IDE interop). So all in all, I considered VS to be a nicer, more consistent overall experience than the one in CLion. I have not tried Qt Creator yet (I know it was among the first to adopt cmake-server), but will do soon, as I will also revisit CLion once they call the MSVC experience baked. ps.: I found it strange that CLion still seems to rely on Codeblock NMake Makefiles for both executing a build AND also hooking the IntelliSense experience into the IDE. Correct me if I’m wrong, but I thought CLion will be the first to adopt cmake-server. ps2.: Big brother VS is already at executing builds with Ninja by default. ps3.: once this (link) issue is fixed in relation to the cmake-tools extension, I’ll consider VS Code for serious work. It has other nice benefits that big brother VS does not. Feladó: Jean-Michaël Celerier Elküldve: 2017. augusztus 18., péntek 15:37 Címzett: Nagy-Egri Máté Ferenc Másolatot kap: CMake Developers Tárgy: Re: [cmake-developers] C++ IDE > Visual Studio 2017 has the best C/C++ experience with CMake IMHO, Visual Studio's CMake integration is a joke in comparison to QtCreator and CLion. ------- Jean-Michaël Celerier http://www.jcelerier.name On Fri, Aug 18, 2017 at 12:04 PM, Nagy-Egri Máté Ferenc via cmake-developers <cmake-developers@cmake.org> wrote: Impressed with VSCode?? If I saw this post anywhere else than the CMake mailing list, I’d understand, but VSCode with CMake is horrible. The fact that in 2017 I have to set include directories, compiler definitions and target paths manually to have proper IntelliSense (Code navigation and syntax higlight) is absurd. As far as I saw Visual Studio 2017 has the best C/C++ experience with CMake. (Google: Visual Studio Open Folder support with CMake) Feladó: Wesley Smith Elküldve: 2017. augusztus 10., csütörtök 6:38 Címzett: Ivam Pretti Másolatot kap: cmake-developers@cmake.org Tárgy: Re: [cmake-developers] C++ IDE I have been really impressed with VSCode. On Sun, Aug 6, 2017 at 1:52 PM, Ivam Pretti <ivamprett...@gmail.com> wrote: Can you recomend an IDE to code in C/C++? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
