In practice, this gives you an opportunity to use any CMake generator of your choice! And now, we are happy to present to you the new CLion 2019.3 build with this new API supported! With the Visual Studio toolchain, CLion was using something very similar to Makefiles – NMake, but the community expected Visual Studio CMake generators ( CPP-14730).Īs a solution, we considered supporting the CMake server first, but later found a better alternative – the new CMake File API, which was added by the CMake authors as a new and better way to query project information.Ninja is known to be a much faster generator and is one of the most requested alternatives ( CPP-2659). This limitation was caused by the fact that CLion was parsing the output of CMake command run with parameters such as -G “CodeBlocks – Unix Makefiles”, -G "CodeBlocks – MinGW Makefiles", or -G "CodeBlocks – NMake Makefiles" to get information about the project, which made it impossible to change the generator used. However, from the very beginning, we supported only the Makefiles generator. A patch-update for anyone using the previous EAP build will be available shortly.ĬMake remains the most deeply integrated project model in CLion. A new CLion 2019.3 EAP (build 193.4697.8) is now available! Get it from our website, via the Toolbox App, or as a snap package (if you are using Ubuntu).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |