|Re: [cdt-dev] Is CMake support stable?|
There is a "Language Settings Provider" for the Compilation Database. Not sure you are familiar with those providers, but you can have pretty much any kind of providers that feed language settings (macros, includes) to the indexer, it’s an extension point. There is definitely overlap with what is being done in Core build here, because toolchain built-ins detection, output parsers and Compilation Database are duplicated. Language Settings Providers were not hooked up to Core build, although they could have. As it is, you only see the providers’ UI (which is arguably complicated for newcomers) when looking at the properties of a MBS project, under C/C++ General > "Preprocessor Include Paths, macros”. Since this provider (Compilation Database) is independent from the build system you use, you can configure any type of projects that has a compile_commands.json. But with MANY clicks and MANY pitfalls. I use a build generator that has little value to be hooked up to CDT (unlike CMake), but I can manage to generate compile_commands.json and hook up the indexer this way.
I think if you have the time, it would be better to invest in Core build and identify what is missing for you, if anything.
Back to the top