Visual studio code, compiling and running in single command - c++

I have specified a pre-launch task to compile c++ code before launching in the launch.json file.
The build command is outlined in my tasks.json file:
"version": "0.1.0",
"command": "bash",
"isShellCommand": true,
"args": ["-c"],
"showOutput": "always",
"tasks": [
{
"taskName": "g++",
"isBuildCommand": true,
"args": [
"g++ /Users/user/OneDrive/Programming/TicTacToe/TicTacToe.cpp -o /Users/user/OneDrive/Programming/TicTacToe/a.out"
],
"showOutput": "always"
}
]
The output of this when I run this is that I receive a clang error:
clang: error: no input files
I'm not sure why this is happening as when I copy paste this bash command to terminal it works, but for some reason I am getting clang error from visual studio. Can anyone familiar with clang figure out what's wrong here?

The problem was that the string passed included the taskname for some reason.
It worked after I addded
"suppressTaskName": true
to tasks.json

Related

VS Code G++ intellisense settings not working and compiler not running to completion

So I'm trying to use vs code as my ide on linux for the GNU c/c++ toolset.
Thus far not with a great amount of success.
The first part is intellisense.
I am using the Microsoft c/c++ extension for this.
I followed what common sense told me and then I also followed what the extenstion told me to do which ended up being the same thing.
See below. Even after reloading the window intellisense is not working.
{
"configurations": [
{
"name": "Linux",
"includePath": [
"${workspaceFolder}/**",
"/Data/Documents/CensusProject/gdallib/src/compiled/include/**"
],
"defines": [],
"compilerPath": "/usr/bin/gcc",
"cStandard": "gnu17",
"cppStandard": "gnu++17",
"intelliSenseMode": "linux-gcc-x64"
}
],
"version": 4
}
The next part is building.
To build from the commandline I have to do the following:
PKG_CONFIG_PATH=/Data/Documents/CensusProject/gdallib/src/compiled/lib/pkgconfig
LIBRARY_PATH=/Data/Documents/CensusProject/gdallib/src/compiled/lib
LD_LIBRARY_PATH=/Data/Documents/CensusProject/gdallib/src/compiled/lib/
C_INCLUDE_PATH=/Data/Documents/CensusProject/gdallib/src/compiled/include/
CPLUS_INCLUDE_PATH=/Data/Documents/CensusProject/gdallib/src/compiled/include/
export PKG_CONFIG_PATH
export LIBRARY_PATH
export LD_LIBRARY_PATH
export C_INCLUDE_PATH
export CPLUS_INCLUDE_PATH
So I placed these in tasks.json
{
"version": "2.0.0",
"tasks": [
{
"type": "cppbuild",
"label": "C/C++: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "${fileDirname}",
"env":{
"PKG_CONFIG_PATH":"/Data/Documents/CensusProject/gdallib/src/compiled/lib/pkgconfig",
"LIBRARY_PATH":"/Data/Documents/CensusProject/gdallib/src/compiled/lib",
"LD_LIBRARY_PATH":"/Data/Documents/CensusProject/gdallib/src/compiled/lib/",
"C_INCLUDE_PATH":"/Data/Documents/CensusProject/gdallib/src/compiled/include/",
"CPLUS_INCLUDE_PATH":"/Data/Documents/CensusProject/gdallib/src/compiled/include/"
}
},
"problemMatcher": [
"$gcc"
],
"group": "build",
"detail": "compiler: /usr/bin/g++"
}
]
}
Running the task lead to
Starting build...
/usr/bin/g++ -g /Data/Documents/CensusProject/gdallib/src/compiled/GdalTest/test.cpp -o /Data/Documents/CensusProject/gdallib/src/compiled/GdalTest/test
collect2: fatal error: cannot find 'ld'
compilation terminated.
Build finished with error(s).
The terminal process terminated with exit code: -1.
which is a bit of an improvement, as before the compiler errored about not finding the header files etc... its sort of an improvement.
in the shell this works fine.
Is anyone else familiar with these problems ?
Thanks in advance.
In your case, the directory where the "ld" program was located had not been defined in the PATH environment variable. Firstly you should add it.
Example:-
export
PATH=$PATH:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin

gdb C++ debugger not working properly on Windows; Visual Studio Code Debugger

Overview
I have been trying to get C++ debugging to work in VS Code for quite some time now with no success.
I followed the official guide from Microsoft on setting up debugging in VS Code, but still ran into problems.
For context:
VS Code config files
launch.json
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "g++.exe - Build and debug active file",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}\\${fileBasenameNoExtension}.exe",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "C:\\Program Files\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin\\gdb.exe",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
],
"preLaunchTask": "C/C++: g++.exe build active file"
}
]
}
tasks.json
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "C/C++: g++.exe build active file",
"command": "C:\\Program Files\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin\\g++.exe",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}\\${fileBasenameNoExtension}.exe"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": ["$gcc"],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
The issue
The problem branches out into two parts.
1. Firstly, I normally use git bash as my default shell in Windows, and would like to keep it that way when debugging C++. However, something that seems to be specific to it is an issue with paths. It seems that running the task here leads to the shell ignoring slashes between directories (likely because of the disparate file system interpretations). This can be seen in the following example:
> Executing task: 'C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin\g++.exe' -g C:\Users\Redact\Desktop\code\Competitive_Programming\Evaluation.cpp -o C:\Users\Redact\Desktop\code\Competitive_Programming\Evaluation.exe <
g++.exe: error: C:UsersRedactDesktopcodeCompetitive_ProgrammingEvaluation.cpp: No such file or directory
g++.exe: fatal error: no input files
compilation terminated.
The terminal process "C:\Program Files\Git\bin\bash.exe '-c', ''C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin\g++.exe' -g C:\Users\Redact\Desktop\code\Competitive_Programming\Evaluation.cpp -o C:\Users\Redact\Desktop\code\Competitive_Programming\Evaluation.exe'" terminated with exit code: 1.
2. When running the debugger with either PowerShell or cmd as the shell, pre-build works as intended and a debugging session is opened, but nothing else happens. The code doesn't stop in the main function (as the guide stated it should) nor are any breakpoints hit—indicating it's not running at all:
(Click Here to see moving gif if it appears still here)
Any help is very much appreciated.

Why does debugging c++ using gdb in vscode create a an executable called launch.exe despite me specifying a name?

When debugging a cpp file in Visual studio code the launch.json seems to be making a launch.exe even though I specified in the tasks that the output file should be called "main.exe" and on top of that there's a build error yet the executable made runs correctly.
All files are in the same directory and the only folder in this directory is the automatically generated .vscode folder
My task.json :
{
"version": "2.0.0",
"tasks": [
{
"type": "cppbuild",
"label": "C/C++: g++.exe build active file",
"command": "C:\\Program Files\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin\\g++.exe",
"args": [
"-g",
"${workspaceFolder}\\*.cpp",
"-o",
"${fileDirname}\\main.exe"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": [
"$gcc"
],
"group": {"kind" : "build","isDefault": true},
"detail": "compiler: \"C:\\Program Files\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin\\g++.exe\""
}
]
}
My launch.json:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "g++.exe - Build and debug active file",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}\\main.exe",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"miDebuggerPath": "C:\\Program Files\\mingw-w64\\x86_64-8.1.0-posix-seh-rt_v6-rev0\\mingw64\\bin\\gdb.exe",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
],
"preLaunchTask": "C/C++: g++.exe build active file"
}
]
}
And then the actual cpp files :
main.cpp
#include "Log.h"
int main()
{
Log("Hello World");
}
Log.cpp
#include "Log.h"
#include <iostream>
void Log(const char* message)
{
std::cout << message << "!\n";
}
And a header file
Log.h
#pragma once
void Log(const char* message);
What I expect to happen is that the tasks.json gets all the cpp files compiled and linked then creates an executable called main.exe.
This does happen when I just run the build task through Terminal > Run Build Task... but when I try debugging by pressing F5 when on my main.cpp file, there is a build error and, in my directory, a launch.exe executable is created. I am then prompted that there were build errors and after clicking "debug anyway", a prompt appears showing that "main.exe" does not exist.
The build error :
C:\Users\Me\AppData\Local\Temp\ccUAuPNe.o: In function `main':
c:/Users/Me/Projects/test/main.cpp:7: undefined reference to `Log(char const*)'
collect2.exe: error: ld returned 1 exit status
The terminal process failed to launch (exit code: -1).
My platform is windows and
I believe I have all the necessary extensions installed correctly so I don't really understand what causes this issue.
It does debug correctly when I change the "program" value in launch.json to "${fileDirname}\launch.exe" (although there is still the build error) but why is launch.exe being made and why are there build errors when debugging but no build errors when going through Terminal > Run Build Task... ?

Setup vscode to compile C files

Im trying to setup vscode to compile and run C files, but I am having problems with setting up the tasks.json file.
I guess what I'm really asking is how to include code from outside the main file. Im trying to include a file "stack.h" from a folder "include" but it's not working.
I get this error in vscode:
ld: can't link with a main executable file 'gcc' for architecture
x86_64 clang: error: linker command failed with exit code 1 (use -v to
see invocation) The terminal process terminated with exit code: 1
My tasks.json file looks like this
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "gcc build active file",
"command": "/usr/bin/gcc",
"args": [
"gcc",
"-o",
"stack_test",
"-I${fileDirname}/../include/",
"${file}",
"${fileDirname}/../src/stack/stack.c",
],
"options": {
"cwd": "/usr/bin"
},
"problemMatcher": [
"$gcc"
],
"group": "build"
}
]
}
I can compile this file normally through the terminal with the following
gcc -o stack_test -I../include/ stack_test.c ../src/stack/stack.c
What am I missing here?
The problem could be that the compiler is not in the platform path. Visual Studio Code is therefore not able to find it.
See: https://code.visualstudio.com/docs/languages/cpp

Visual Studio Code with Bash Terminal (WSL) in C++ builds only .out files - not .exe

I'm using Visual Studio Code on Windows 10 with the Linux Subsystem. (Ubuntu)
I've created a small c++ file and when I'm building it with the bash terminal - only a .out file is created. Which is fine, but I want to debug it as well and in that case - I can only open .exe files.
When I switch to powershell from bash - the build extension is an .exe
tasks.json
{
"version": "2.0.0",
"tasks": [
{
"label": "echo",
"type": "shell",
"command": "g++",
"args": [
"-g", "main.cpp"
],
"group": { "kind": "build", "isDefault": true }
}
]
}
launch.json for debugging
{
"name": "(gdb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/a.exe", // .out doesn't work here
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": true,
"MIMode": "gdb",
"miDebuggerPath": "C:\\MinGW\\bin\\gdb.exe",
"preLaunchTask": "echo",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
]
}
main.cpp
#include <iostream>
int main() {
std::cout << "hello a" << std::endl;
}
I'm really not sure what to do - as I'm not able to debug .out files and I'd like to choose the build extension myself.
Found the solution:
sudo apt-get install mingw-w64
And then inside tasks.json
"command": "i686-w64-mingw32-g++"
That compiles a 32 bit exe - but the 64 bit version with x86_64-w64-mingw32-g++ somehow doesn't work. Creates an invalid exe.
In order to run/debug cross-platform, your have to use cross-compilers such as MinGW. You can install MinGW-w64 in both Windows, Linux (or WSL).
VScode-tools with gdb.exe from MinGW can debug *.out as well as *.exe files (Tested).
To compile 64-bit version you need to include some static depedency library for C/C++ which are libgcc and libstdc++ while compile. so the command and args in task.json should be:
"command": "x86_64-w64-mingw32-g++",
"args": [
"-g", //Need for debug and compatibility
"-static-libgcc", //flag for the libgcc
"-static-libstdc++", //flag for the libgc++
"helloworld.cpp", //C++ source code
"-o", //flag for output
"a2.out" //Output filename and extension (can be .exe)
],
You can learn more about C/C++ Standard Library Dependencies here