We use some custom build system (not vanilla make). Generally, we don't build code (C++) in the sandbox and create linked area (directory with soft links to files in the sandbox) to do the build there. For debug and optimized builds, I may have 2 such paths. And I want to define 2 different tasks for triggering opt or debug builds ...

For experimenting with defining tasks, I wanted to define 2 dummy tasks - echo full path of build.log from the opt build area, and another to echo full path of build.log from the debug build area.

I tried following:

{
    "version": "2.0.0",
    "options": {
        "env": {
            "OPT_BUILD": "<some common path>/opt",
            "DBG_BUILD": "<some common path>/dbg"
        },
    },
    "tasks": [
        {
            "label": "Echo Full Opt-Build Log Name",
            "type": "shell",
            "command": "echo",
            "args": ["${env:OPT_BUILD}/build.log"],
            "presentation": {
                "reveal": "always",
                "panel": "new"
            }
        },
        {
            "label": "Echo Full Dbg-Build Log Name",
            "type": "shell",
            "command": "echo",
            "args": ["${env:DBG_BUILD}/build.log"],
            "presentation": {
                "reveal": "always",
                "panel": "new"
            }
        },
    ]
}

However, when I run any of these, it just prints /build.log. How to fix it?

I don't want to move the options inside tasks. The doc says following:

Options can be set per task but also globally or per platform. Environment variables configured here can only be referenced from within your task script or process and will not be resolved if they are part of your args, command, or other task attributes.

My VS Code version is 1.96.2

We use some custom build system (not vanilla make). Generally, we don't build code (C++) in the sandbox and create linked area (directory with soft links to files in the sandbox) to do the build there. For debug and optimized builds, I may have 2 such paths. And I want to define 2 different tasks for triggering opt or debug builds ...

For experimenting with defining tasks, I wanted to define 2 dummy tasks - echo full path of build.log from the opt build area, and another to echo full path of build.log from the debug build area.

I tried following:

{
    "version": "2.0.0",
    "options": {
        "env": {
            "OPT_BUILD": "<some common path>/opt",
            "DBG_BUILD": "<some common path>/dbg"
        },
    },
    "tasks": [
        {
            "label": "Echo Full Opt-Build Log Name",
            "type": "shell",
            "command": "echo",
            "args": ["${env:OPT_BUILD}/build.log"],
            "presentation": {
                "reveal": "always",
                "panel": "new"
            }
        },
        {
            "label": "Echo Full Dbg-Build Log Name",
            "type": "shell",
            "command": "echo",
            "args": ["${env:DBG_BUILD}/build.log"],
            "presentation": {
                "reveal": "always",
                "panel": "new"
            }
        },
    ]
}

However, when I run any of these, it just prints /build.log. How to fix it?

I don't want to move the options inside tasks. The doc says following:

Options can be set per task but also globally or per platform. Environment variables configured here can only be referenced from within your task script or process and will not be resolved if they are part of your args, command, or other task attributes.

My VS Code version is 1.96.2

• visual-studio-code
• vscode-tasks

1 Answer 1

Resolved after changing

            "args": ["${env:OPT_BUILD}/build.log"],

to

            "args": ["${OPT_BUILD}/build.log"],