You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, the if add_extra_clang_flags: branch in PrepareFlagsForClang function in file ycmd/ycmd/completers/cpp/flags.py. Otherwise, the result when complete headers is super noisy when somebody uses g++ rather than clang on macOS
The text was updated successfully, but these errors were encountered:
I don't think that is a good idea. That branch that reaches into AddMacIncludePaths is also responsible for adding -resource-dir= and -fno-delayed-template-parsing on Windows. I've done invasive changes in flags.py before and it was very frustrating.
That said, you can still avoid that by:
Switching to the clangd based completer
Using compilation databases instead of the extra conf files.
I actually had reason to need this recently myself for some very bizarre reasons so maybe I will add it at some point.
puremourning
changed the title
Add option to disable the extra clang flags in MacOS
Add option to disable the extra clang flags in MacOS [Feature Request]
Mar 24, 2022
In particular, the
if add_extra_clang_flags:
branch inPrepareFlagsForClang
function in file ycmd/ycmd/completers/cpp/flags.py. Otherwise, the result when complete headers is super noisy when somebody uses g++ rather than clang on macOSThe text was updated successfully, but these errors were encountered: