Add support for environment variables

Open
  • Is something wrong?
#680 2 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
developer-experience, tooling

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.

Description

Feature: Configuration Feature: launch

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.

Dominant language
TypeScript
Stars
245
Forks
79
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-makefile-tools

All issues in microsoft/vscode-makefile-tools

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.