microsoft / microsoft/vscode-makefile-tools
Add support for environment variables
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
I am working on a dynamically linked library project and it would be nice to be able to set LD_LIBRARY_PATH to a local directory prior to running or debugging the test programs. By the way, I have limited understanding of vs code plugins, so perhaps I am just missing something. In my launch.json I have something like this:
"environment": [ { "name": "LD_LIBRARY_PATH", "value": "../lib" } ],
which works to set the library path prior to executing. When I try to add the same to the settings.json makefile.launchConfigurations it does not set the environment var and the launch fails.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare how environment variables are handled in launch.json with makefile.launchConfigurations in settings.json. Reproduce the dynamically linked library case using LD_LIBRARY_PATH and verify that a configured variable is present before the test program runs or under debugging; done means the launch succeeds with the configured local library path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100