VSCode call WSL's make

[ghost]

When I configured dev environment at WSL, I trying to using tasks.json to call WSL side's make, but, the terminal say: bash: 'make' not found.
My WSL system is Ubuntu 18.04, use zsh(oh-my-zsh)

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• WSL install not found (#63008)
• WSL TERMINAL (#61553)
• Calling code . from WSL prompt does not return (#62698)
• wsl apps executable (#58251)
• How to configure a task to run in WSL? (#14898)

[ghost]

VSCode can add support for WSL's side build tool? Like make,cmake.

[alexr00]

What is the output of make --version in WSL?

[ghost]

bash: make: command not found.

[ghost]

When I use tasks to call it

[alexr00]

What is the output of make --version in WSL when you run it without tasks though?

[ghost]

GNU Make 4.2.1

[alexr00]

What do you have terminal.integrated.shell.windows set to in your settings? Are you setting the terminal exectuable to zsh there, or in your tasks.json?

[ghost]

I set that, and i set command at tasks.json.terminal.intergrated.shell.windowsI set to wsl.exe.

[alexr00]

It looks like we don't do the special handling for wsl.exe that we do for bash.exe. I know bash.exe is no longer recommended for WSL, but could you try setting terminal.integrated.shell.windows to bash.exe? I will fix it for wsl.exe, but using bash.exe for now will get you unstuck.

[ghost]

Ok,Thanks for your answer.

[alexr00]

Verification steps for later:
On Windows, setup WSL.
In settings: "terminal.integrated.shell.windows": "wsl.exe",
Run a task. Example:

	{
		"type": "shell",
		"label": "echo",
		"command": "echo hello",
		"problemMatcher": []
	}

The task should run and not have the message: /bin/bash: /d: No such file or directory
The terminal process terminated with exit code: 127

[chrmarti]

@alexr00 There is still an error:

[alexr00]

@chrmarti, I can't reproduce this. What version of Windows are you on?
I think this is a different bug. In your issue wsl.exe can't handle -, but in the original bug it couldn't handle /d.

[chrmarti]

@alexr00 This is 10.0.17134.

[alexr00]

@chrmarti can you try running wsl.exe -e echo hello from cmd.exe? Can you paste the output of running wsl.exe --help from cmd.exe?

[chrmarti]

Microsoft Windows [Version 10.0.17134.523]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Users\chrmarti>wsl.exe -e echo hello
/bin/bash: - : invalid option

C:\Users\chrmarti>wsl.exe --help
/bin/bash: --: invalid option
Usage:  /bin/bash [GNU long option] [option] ...
        /bin/bash [GNU long option] [option] script-file ...
GNU long options:
        --debug
        --debugger
        --dump-po-strings
        --dump-strings
        --help
        --init-file
        --login
        --noediting
        --noprofile
        --norc
        --posix
        --rcfile
        --restricted
        --verbose
        --version
Shell options:
        -ilrsD or -c command or -O shopt_option         (invocation only)
        -abefhkmnptuvxBCHP or -o option

[alexr00]

Thank you! Looks like there would need to be a Windows version check since the build that you're on appears to just wrap bash.exe and the more recent build that I'm on has different argument options:

C:\Users\alros\repos\vscode\vscode>wsl.exe --help
Usage: wsl.exe [option] ...
Options:
    -d, --distribution <DistributionName>
        Launch the specified distribition.

    -e, --exec <CommandLine>
        Execute the specified Linux command. The remainder of the arguments are
        used as the command line to execute.

    -u, --user <UserName>
        Run as the specified user.

    --help
        Display this usage information.

    --
        Stop parsing arguments and pass the remainder to the Linux process.

This is a different problem, so I opened a new issue: #67855