Using a shell command as VSCode task variable value

Question

I am trying to define a VSCode task in tasks.json that would adapt to the specific architecture where VSCode runs. To do this, I want to get the architecture as uname --m (e.g. "aarch64" or "amd64"). My goal is to interpolate the output of uname into an environment variable like so

"version": "2.0.0",
"tasks": [
    {
        "label": "build",
        "type": "shell",
        "command": "cmake",
        "args": [
            "-DMYLIB_INCLUDE_DIR=$MYLIB/include",
            "-DMYLIB_LIBRARY=$MYLIB/lib"
        ],
        "options": {
            "env": {
                "MYLIB": "${workspaceFolder}/mylib/${command:get_arch}"
            }
        },
    }
]

In my case, I will have architecture-specific versions of mylib under mylib/aarch64, mylib/amd64, etc.

My attempt so far as been to define a second get_arch task used in the environment definition of MYLIB, that simply runs uname.

{
    "label": "get_arch",
    "type": "shell",
    "command": "uname --m"
}

Of course, this task is not a proper command and so it isn't detected by VSCode and my build task fails. I checked out the documentation on variable substition, but they don't mention if it's possible to substitute a shell command. I guess this would be possible from within an extension, but I want to keep things as simple as possible.

leeroycool · Accepted Answer · 2019-11-26 02:07:25Z

20

+50

This extension provides a way to launch arbitrary shell commands as a VS Code command:

"tasks": [
    {
        "label": "test_arch",
        "type": "shell",
        "command": "echo",
        "args": [
            "${MYARCH}"
        ],
        "options": {
            "env": {
                "MYARCH": "${input:get_arch}"
            }
        },
        "problemMatcher": []
    },
],
"inputs": [
    {
        "id": "get_arch",
        "type": "command",
        "command": "shellCommand.execute",
        "args": {
            "command": "uname -m"
        }
    }
]

One disadvantage I discovered is that you have to press Enter once more when the result of the command is prompted in picker. Aside of this, this is the straightest way to implement what you want, and yet it can be utilized in many similar situations.

Alternatively, you can add pickString input with arch picker or create an extension that adds only single command GetArch.

edited Nov 26, 2019 at 2:07

leeroycool

232 bronze badges

answered Nov 19, 2019 at 9:34

Dmitry Vornychev

6455 silver badges12 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Shwabster · Accepted Answer · 2020-03-16 13:20:24Z

6

If you don't want to press enter every time, you can add the option useFirstResult: true in the args section.

edited Mar 16, 2020 at 13:20

Shwabster

4871 gold badge11 silver badges27 bronze badges

answered Mar 16, 2020 at 11:33

Paul Bhs

691 silver badge2 bronze badges

1 Comment

KyleMit Over a year ago

fyi - This might serve better as a comment on Dmitriy Vornychev's answer as an iteration of that solution, rather than an independent answer

Collectives™ on Stack Overflow

Using a shell command as VSCode task variable value

2 Answers 2

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related