Closed CalebDu closed 1 year ago
clangd.fallbackFlags
is only used for source files for which a compile_commands.json
file cannot be found. In this case, clangd is successfully finding /home/caleb.du/code/tops/build/compile_commands.json
, so fallbackFlags
will not be used.
For adding an extra flag to the command from compile_commands.json
, you can create a .clangd
config file containing:
CompileFlags:
Add: [-I/home/caleb.du/code/tops/build/3rdparty/clang_binary/src/lib/clang/11.0.0/include/]
See https://clangd.llvm.org/config.html#add for more details.
clangd.fallbackFlags
is only used for source files for which acompile_commands.json
file cannot be found. In this case, clangd is successfully finding/home/caleb.du/code/tops/build/compile_commands.json
, sofallbackFlags
will not be used.For adding an extra flag to the command from
compile_commands.json
, you can create a.clangd
config file containing:CompileFlags: Add: [-I/home/caleb.du/code/tops/build/3rdparty/clang_binary/src/lib/clang/11.0.0/include/]
See https://clangd.llvm.org/config.html#add for more details.
thank you, i fix it.
because my huge project can't find some header file. I add -I flag in clangd.fallbackFlag. but i does not work. And in clangd extension "output" there is no "fallbackFlag" information. setting.json
Logs
System information Clangd version (from the log, or
clangd --version
): 16.0.2 clangd extension version:0.1.24 Operating system:ubuntu16.04 docker