Open danmoseley opened 5 years ago
I added a .vscode/c_cpp_properties.json in https://github.com/dotnet/coreclr/pull/24540 to get better Go To Definition in VS Code in the VM code.
.vscode/c_cpp_properties.json
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 (https://github.com/microsoft/vscode-cpptools/issues/15) which would make good VS Code integration more valuable than before.
Hoping this should be improved/addressed with the cmake work @jkoritzinsky is doing.
Marking as future.
I added a
.vscode/c_cpp_properties.json
in https://github.com/dotnet/coreclr/pull/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 (https://github.com/microsoft/vscode-cpptools/issues/15) which would make good VS Code integration more valuable than before.