[Enhancement]: Expose Alire's workspace environment variables to VSCode Launch

[Joebeazelman]

Enhancement Request

VSCode is unaware of Alire's workspace environment variables during launches, which are required for configuring and launching Alire installed and managed tools. When configuring VSCode's debugger, for instance, its GDB executable path has to be: hardcoded, stored in the PATH, or obtained through a complex workaround. All these options are less than ideal. The first option breaks if any of the settings change. The second only works for the executable path and doen't support more than one toolchain. The last one isn't portable across platforms.

The solution is to inject Alire's environment variables before a launch is executed.

[AnthonyLeonardoGracio]

Hello @Joebeazelman,

Indeed, currently only the ALS environment gets modified according to Alire's workspace.

What you are asking is to modify the whole VS Code instance environment when working on an Alire workspace, right?

Regards,

[Joebeazelman]

Yes. Although I think you should have the option to turn it off in order to prevent any runtime conflicts.

[AnthonyLeonardoGracio]

We will create an internal issue to address this. Thanks for the report.

Regards,