I added a .vscode/c_cpp_properties.json in dotnet/coreclr#24540 to get better Go To Definition in VS Code in the VM code.
Unfortunately this required pasting in lots of include paths and defines that would be better to be discovered from the build process.
It looks like VS Code support CMAKE "compile commands" may allow us to achieve that:
https://cmake.org/cmake/help/v3.5/variable/CMAKE_EXPORT_COMPILE_COMMANDS.html
BTW, The C++ Find All References shipped last month (microsoft/vscode-cpptools#15) which would make good VS Code integration more valuable than before.
I added a
.vscode/c_cpp_properties.jsonin dotnet/coreclr#24540 to get better Go To Definition in VS Code in the VM code.Unfortunately this required pasting in lots of include paths and defines that would be better to be discovered from the build process.
It looks like VS Code support CMAKE "compile commands" may allow us to achieve that:
https://cmake.org/cmake/help/v3.5/variable/CMAKE_EXPORT_COMPILE_COMMANDS.html
BTW, The C++ Find All References shipped last month (microsoft/vscode-cpptools#15) which would make good VS Code integration more valuable than before.