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
tcframe script directly invoke g++ and uses custom include paths -I "$TCFRAME_HOME/include". This causes a bunch of errors to the code editor that uses LSP with default config:
One solution is to generate compile_commands.json to tell the LSP how the compilation is done. For example, the following is a compile_commands.json that I handcraft for my own usage (with /absolute/bath/to/working/directory replaced).
tcframe script directly invoke g++ and uses custom include paths
-I "$TCFRAME_HOME/include"
. This causes a bunch of errors to the code editor that uses LSP with default config:One solution is to generate
compile_commands.json
to tell the LSP how the compilation is done. For example, the following is acompile_commands.json
that I handcraft for my own usage (with/absolute/bath/to/working/directory
replaced).My proposal is to have tcframe script to generate
compile_commands.json
, e.g. using commandtcframe export_compile_commands
.The text was updated successfully, but these errors were encountered: