[PROS]Who can share the contents of vscode's "c_cpp_properties.json" file?

VEX V5 Technical Support UNOFFICIAL Tech Support
#1

Who can share the contents of vscode’s “c_cpp_properties.json” file?

if i used
“compileCommands”：“ $ {workspaceFolder} /compile_commands.json”
also had problems.
It seems that its “compile_commands.json” settings are incompatible with Windows 10 1809.
I also had problems with cquery server using vsCode.
So I want to try intellisense.

This is my configuration file, but there are many problems with it.

{
“configurations”:
{
“name”: “vex”,
“includePath”:
“{workspaceFolder}/**", "{workspaceFolder}/include”,
“c:\program files\pros\toolchain\usr\bin\…/lib/gcc/arm-none-eabi/7.2.1/…/…/…/…/arm-none-eabi/include/c++/7.2.1”,
“c:\program files\pros\toolchain\usr\bin\…/lib/gcc/arm-none-eabi/7.2.1/…/…/…/…/arm-none-eabi/include/c++/7.2.1/arm-none-eabi/thumb/v7-ar/fpv3/softfp”,
“c:\program files\pros\toolchain\usr\bin\…/lib/gcc/arm-none-eabi/7.2.1/…/…/…/…/arm-none-eabi/include/c++/7.2.1/backward”,
“c:\program files\pros\toolchain\usr\bin\…/lib/gcc/arm-none-eabi/7.2.1/include”,
“c:\program files\pros\toolchain\usr\bin\…/lib/gcc/arm-none-eabi/7.2.1/include-fixed”,
“c:\program files\pros\toolchain\usr\bin\…/lib/gcc/arm-none-eabi/7.2.1/…/…/…/…/arm-none-eabi/include”
],
“defines”:
“_POSIX_THREADS”,
“_UNIX98_THREAD_MUTEX_ATTRIBUTES”
],
“limitSymbolsToIncludedHeaders”: true,
“compilerPath”: “C:\cquery\build\LLVM-7.0.0-win64\bin\clang++.exe”,
“cStandard”: “c11”,
“cppStandard”: “c++17”,
“intelliSenseMode”: “clang-x64”
}
],
“version”: 4
}

1.jpg

#2

First thing to note is that compile_commands.json is not necessarily transferable between different computers (or different users) as the paths of files would be computer-and-user-dependent.

Second thing to note, we use compile_commands.json with cquery within PROS. I know there is a VS Code plugin for cquery, so you may wish to try that. We use scan-build to generate the JSON file, which itself is the core of bear.

#3

Every time I create a new src file, I rebuild compile_commands. json. I don’t know how to configure these manually. Can I publish the necessary options?

#4

You shouldn’t configure compile_command.json manually.


prosv5 build-compile-commands

will do that for you. Recent versions of the CLI will generate the compile_commands.json when running


prosv5 make

if you have PROS Editor installed.

#5