Add VS debugger launch action to VS code configuration

[ronaldfw]

No description provided.

[beckerhe]

Hi Ronald,
I'm looping in Anton since he is the actual vs-code-export.

Cheers,
Henning

[beckerhe]

I think instead of ${workspaceFolder}/build_default_relwithdebinfo}, ${command:cmake.buildDirectory} might work better.

[beckerhe]

But this needs to the cmake-extension and might also not be appropriate for your use case.

[beckerhe]

Ref: microsoft/vscode-cmake-tools#726

[ronaldfw]

Just substituting this naively results in an error for me: "command cmake.buildDirectory not found". Not sure what else I need to do to make this work?

[ronaldfw]

Ah, didn't see your other replies before replying. @antonrohr Let me know what you think we should do here.

[beckerhe]

You're probably not using the cmake extension. In this case it's fine for me to go with your solution. Personally I'm not a big fan of having a .vscode folder in the repo at all, but I'm also not a frequent user of vscode. Anton should have a look.

[antonrohr]

I think ${workspaceFolder}/build_default_relwithdebinfo is fine since its pretty much the standard way of doing that. I don't even know how the cmake extension would decide which build target I want to choose if I have multiple

[ronaldfw]

I don't have an opinion on this, I just want my debugger to work out-of-the box (and I'm just using this one target anyway). Can either of you approve for now? We can always change / improve this later if we find a better way.

[antonrohr]

Suggested change

	"externalConsole": false
	"externalConsole": false,
	"preLaunchTask": "shell: build default relwithdebinfo"

This would always trigger a build before starting the debugging. This is how I have my configuration, but it is purely preference

[antonrohr]

Thanks Ronald for this!

I don't know how you are using this, but maybe it would be good to also set the environment variables or have a second debugging target with the variables.

      "environment": [
        {
          "name": "ORBIT_COLLECTOR_EXECUTABLE_PATH",
          "value": "${workspaceFolder}/build_ggp_release/bin/OrbitService"
        },
        {
          "name": "ORBIT_COLLECTOR_ROOT_PASSWORD",
          "value": "your password"
        }
      ], 

Maybe we could also have a second task for building ggp_release and then have both tasks as prerequisite. Up to you

[ronaldfw]

Thanks Ronald for this!

I don't know how you are using this, but maybe it would be good to also set the environment variables or have a second debugging target with the variables.

      "environment": [
        {
          "name": "ORBIT_COLLECTOR_EXECUTABLE_PATH",
          "value": "${workspaceFolder}/build_ggp_release/bin/OrbitService"
        },
        {
          "name": "ORBIT_COLLECTOR_ROOT_PASSWORD",
          "value": "your password"
        }
      ], 

Maybe we could also have a second task for building ggp_release and then have both tasks as prerequisite. Up to you

I think these are good suggestions that we want to add in the future. I'll merge this for now as it's a big improvement for me that I can just use the VS debugger without local changes and directly in VS code.