BTW, I haven’t factored into how the language settings providers get used by the new build framework at all. Right now it assumes well understood toolchains, which gcc and clang are, and build systems that tell you the options without running a build,
which arduino, qmake, and cmake do.
Standard make/build projects are likely different since you don’t get the options so that may make things difficult when and if we get there.
Doug.
Hi Martin,
GCCBuildCommandParser does not listen to any events neither to resource change events. Moreover, it will check if the language settings for the provided configuration changed and if not it won't serialize
anything. You could put a breakpoint in LanguageSettingsSerializableProvider.isLanguageSettingsProviderStoreChanged(...) to check why it thinks that settings change.
The effect that you are describing could be a result of calling startup()/processLine()/shutdown() sequence on each processed line. That would be just called for many lines and not
endlessly in a loop unless there is a recursion introduced in CMakeLangSetProvider.getSettingsEntries(). How do you implement this method?
Thanks,
Andrew