VSCode build task opens shell and stops without running command
up vote
0
down vote
favorite
I am currently attempting to run a build.bat script that builds my solution with the VSCode build tasks. Unfortunately all it does is open the command prompt without running the actual command as instructed. The task I'm currently attempting to run is
{
"version": "2.0.0",
"tasks": [
{
"label": "build",
"type": "shell",
"windows": {
"options": {
"cwd": "W:\handmade\code",
"shell": {
"args": [
"/k W:\handmade\misc\shell.bat"
]
}
},
"command": "build.bat",
},
"problemMatcher": [
"$gcc"
]
}
]
}
What I'd expect as output is:
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.8.4
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
W:handmadecode>build.bat
A subdirectory or file ....build already exists.
Microsoft (R) C/C++ Optimizing Compiler Version 19.15.26729 for x64
Copyright (C) Microsoft Corporation. All rights reserved.
win32_handmade.cpp
Microsoft (R) Incremental Linker Version 14.15.26729.0
Copyright (C) Microsoft Corporation. All rights reserved.
/out:win32_handmade.exe
/debug
win32_handmade.obj
user32.lib
Which is what I get if I run the command normally, what I get instead is
> Executing task: build.bat <
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.8.4
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
W:handmadecode>
And then it hangs until exit is called. The command provided in the tasks.json is clearly never attempted executed and I'm at my wit's end as to why this is.
batch-file cmd visual-studio-code vscode-settings vscode-tasks
asked Nov 19 at 18:05
Troels Jessen
358
add a comment |
up vote
0
down vote
favorite
I am currently attempting to run a build.bat script that builds my solution with the VSCode build tasks. Unfortunately all it does is open the command prompt without running the actual command as instructed. The task I'm currently attempting to run is
{
"version": "2.0.0",
"tasks": [
{
"label": "build",
"type": "shell",
"windows": {
"options": {
"cwd": "W:\handmade\code",
"shell": {
"args": [
"/k W:\handmade\misc\shell.bat"
]
}
},
"command": "build.bat",
},
"problemMatcher": [
"$gcc"
]
}
]
}
What I'd expect as output is:
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.8.4
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
W:handmadecode>build.bat
A subdirectory or file ....build already exists.
Microsoft (R) C/C++ Optimizing Compiler Version 19.15.26729 for x64
Copyright (C) Microsoft Corporation. All rights reserved.
win32_handmade.cpp
Microsoft (R) Incremental Linker Version 14.15.26729.0
Copyright (C) Microsoft Corporation. All rights reserved.
/out:win32_handmade.exe
/debug
win32_handmade.obj
user32.lib
Which is what I get if I run the command normally, what I get instead is
> Executing task: build.bat <
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.8.4
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
W:handmadecode>
And then it hangs until exit is called. The command provided in the tasks.json is clearly never attempted executed and I'm at my wit's end as to why this is.
batch-file cmd visual-studio-code vscode-settings vscode-tasks
asked Nov 19 at 18:05
Troels Jessen
358
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am currently attempting to run a build.bat script that builds my solution with the VSCode build tasks. Unfortunately all it does is open the command prompt without running the actual command as instructed. The task I'm currently attempting to run is
{
"version": "2.0.0",
"tasks": [
{
"label": "build",
"type": "shell",
"windows": {
"options": {
"cwd": "W:\handmade\code",
"shell": {
"args": [
"/k W:\handmade\misc\shell.bat"
]
}
},
"command": "build.bat",
},
"problemMatcher": [
"$gcc"
]
}
]
}
What I'd expect as output is:
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.8.4
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
W:handmadecode>build.bat
A subdirectory or file ....build already exists.
Microsoft (R) C/C++ Optimizing Compiler Version 19.15.26729 for x64
Copyright (C) Microsoft Corporation. All rights reserved.
win32_handmade.cpp
Microsoft (R) Incremental Linker Version 14.15.26729.0
Copyright (C) Microsoft Corporation. All rights reserved.
/out:win32_handmade.exe
/debug
win32_handmade.obj
user32.lib
Which is what I get if I run the command normally, what I get instead is
> Executing task: build.bat <
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.8.4
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
W:handmadecode>
And then it hangs until exit is called. The command provided in the tasks.json is clearly never attempted executed and I'm at my wit's end as to why this is.
batch-file cmd visual-studio-code vscode-settings vscode-tasks
asked Nov 19 at 18:05
Troels Jessen
358
I am currently attempting to run a build.bat script that builds my solution with the VSCode build tasks. Unfortunately all it does is open the command prompt without running the actual command as instructed. The task I'm currently attempting to run is
{
"version": "2.0.0",
"tasks": [
{
"label": "build",
"type": "shell",
"windows": {
"options": {
"cwd": "W:\handmade\code",
"shell": {
"args": [
"/k W:\handmade\misc\shell.bat"
]
}
},
"command": "build.bat",
},
"problemMatcher": [
"$gcc"
]
}
]
}
What I'd expect as output is:
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.8.4
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
W:handmadecode>build.bat
A subdirectory or file ....build already exists.
Microsoft (R) C/C++ Optimizing Compiler Version 19.15.26729 for x64
Copyright (C) Microsoft Corporation. All rights reserved.
win32_handmade.cpp
Microsoft (R) Incremental Linker Version 14.15.26729.0
Copyright (C) Microsoft Corporation. All rights reserved.
/out:win32_handmade.exe
/debug
win32_handmade.obj
user32.lib
Which is what I get if I run the command normally, what I get instead is
> Executing task: build.bat <
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.8.4
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************
[vcvarsall.bat] Environment initialized for: 'x64'
W:handmadecode>
And then it hangs until exit is called. The command provided in the tasks.json is clearly never attempted executed and I'm at my wit's end as to why this is.
batch-file cmd visual-studio-code vscode-settings vscode-tasks
batch-file cmd visual-studio-code vscode-settings vscode-tasks
asked Nov 19 at 18:05
Troels Jessen
358
asked Nov 19 at 18:05
Troels Jessen
358
asked Nov 19 at 18:05
Troels Jessen
358
asked Nov 19 at 18:05
Troels Jessen
358
asked Nov 19 at 18:05
Troels Jessen
358
358
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380331%2fvscode-build-task-opens-shell-and-stops-without-running-command%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
