VS Code, and presumably other debuggers, allow you to configure the debugger that gets used for the visual debugger. This involves editing/creating .vscode/tasks.json and also .vscode/launch.json. It would be handy if the container could automatically create these files in the project folder it gets called into, so then the user can just select a "Debug with CAEN" option to automatically use the container for debugging.
The biggest issue with this is will be configuring the launch.json file. Many projects need file input and CLI args in order to even start, which means that either the user will need to manually configure these or the container somehow needs to predict what to use. What might work is simply adding a generic option to any existing launch.json and then telling the user to change the values that they need and how to do that.
VS Code, and presumably other debuggers, allow you to configure the debugger that gets used for the visual debugger. This involves editing/creating
.vscode/tasks.json
and also.vscode/launch.json
. It would be handy if the container could automatically create these files in the project folder it gets called into, so then the user can just select a "Debug with CAEN" option to automatically use the container for debugging.The biggest issue with this is will be configuring the
launch.json
file. Many projects need file input and CLI args in order to even start, which means that either the user will need to manually configure these or the container somehow needs to predict what to use. What might work is simply adding a generic option to any existinglaunch.json
and then telling the user to change the values that they need and how to do that.