-
Notifications
You must be signed in to change notification settings - Fork 252
expose openocdPath
in launch.json?..
#111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This should be added to the next release |
@Marus, @busticated I am currently using
It is becoming more common to make this (and arm tool chain) project-specific even in my use case. So, in my launch.json, I use This is mainly because, in settings.json, we cannot make things OS specific. Also a problem with multi-root VSCode workspaces. Global user settings is also an option... just hard to find and edit. |
For every path mentioned for user/workspace settings, there is now a OS-specific setting. This will work better for users using the sync feature. This is also the method used by VSCode itself. I recommend using this mechanism rather than
|
hi there 👋
very similar request as: #51 and for the same reasons as mentioned in #110
would it be possible to expose the
openocdPath
setting inlaunch.json
as well?currently, i end up managing the setting at the workspace level on behalf of my users based on other configuration settings. so the flow is like: 1. tweak seemingly unrelated setting 2. update toolchain paths & dependencies 3. set
cortex-debug.openocdPath
in the.code-workspace
file based on steps 1 and 2.instead, being able to do something like this in
launch.json
would be nice:i'm running:
macOS: 10.13.6 (high sierra)
VSCode: 1.29.1
Cortex Debug: 0.1.21
The text was updated successfully, but these errors were encountered: