Note that I'm using VS Code on Ubuntu 17.10 and using the GCC Compiler.
I'm having trouble building a simple program which makes use of additional .ccp files. I'm probably missing something obvious here as I'm fairly new to programming but I'll explain what I've done so far. This is something that is stopping me from continuing with a tutorial I'm doing.
I have written a very simple program to demonstrate my point as follows.
main.ccp
#include <iostream>
#include "Cat.h"
using namespace std;
int main ()
{
speak();
return 0;
}
Cat.h
#pragma once
void speak();
Cat.ccp
#include <iostream>
#include "Cat.h"
using namespace std;
void speak()
{
std::cout << "Meow!!" << std::endl;
}
This simple program builds in both Codeblocks and Visual Studio Community 2017 no problem and I can't figure out what I need to do to make it run.
This error at the bottom indicates that the Cat.ccp file is not being picked up at all. If I was to drop the definition from this Cat.ccp into the header file the program compiles and runs fine but I need to make use of that .ccp file as I understand this is the accepted way of separating code. I'll note that all the files are in the same folder too.
I understand that I may need to tell VS Code where to look for the Cat.ccp file but it's strange to me that it finds the header in the same location. Nevertheless, after looking online I've been reading that I may need to place a directory into the c_cpp_intellisense_properties.json. Here's what mine looks like.
{
"configurations": [
{
"name": "Mac",
"includePath": [
"/usr/include",
"/usr/local/include",
"${workspaceRoot}"
],
"defines": [],
"intelliSenseMode": "clang-x64",
"browse": {
"path": [
"/usr/include",
"/usr/local/include",
"${workspaceRoot}"
],
"limitSymbolsToIncludedHeaders": true,
"databaseFilename": ""
},
"macFrameworkPath": [
"/System/Library/Frameworks",
"/Library/Frameworks"
]
},
{
"name": "Linux",
"includePath": [
"/usr/include/c++/7",
"/usr/include/x86_64-linux-gnu/c++/7",
"/usr/include/c++/7/backward",
"/usr/lib/gcc/x86_64-linux-gnu/7/include",
"/usr/local/include",
"/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed",
"/usr/include/x86_64-linux-gnu",
"/usr/include",
"/home/danny/Documents/C++_Projects/24_-_Classes/Cat.cpp",
"${workspaceRoot}",
"/home/danny/Documents/C++_Projects/24_-_Classes/",
"/home/danny/Documents/C++_Projects/24_-_Classes/.vscode",
"/home/danny/Documents/C++_Projects/24_-_Classes/.vscode/Cat.cpp"
],
"defines": [],
"intelliSenseMode": "clang-x64",
"browse": {
"path": [
"/usr/include/c++/7",
"/usr/include/x86_64-linux-gnu/c++/7",
"/usr/include/c++/7/backward",
"/usr/lib/gcc/x86_64-linux-gnu/7/include",
"/usr/local/include",
"/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed",
"/usr/include/x86_64-linux-gnu",
"/usr/include",
"${workspaceRoot}",
"/home/danny/Documents/C++_Projects/24_-_Classes/",
"/home/danny/Documents/C++_Projects/24_-_Classes/.vscode/Cat.cpp"
],
"limitSymbolsToIncludedHeaders": true,
"databaseFilename": ""
}
},
{
"name": "Win32",
"includePath": [
"C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/include",
"${workspaceRoot}"
],
"defines": [
"_DEBUG",
"UNICODE"
],
"intelliSenseMode": "msvc-x64",
"browse": {
"path": [
"C:/Program Files (x86)/Microsoft Visual Studio 14.0/VC/include/*",
"${workspaceRoot}"
],
"limitSymbolsToIncludedHeaders": true,
"databaseFilename": ""
}
}
],
"version": 3
}
At one point I wondered if I need to add a double command in there to tell the compiler to build both .ccp files in the tasks.json but I haven't managed to figure out how to do that, or even if that's the right approach.
tasks.json
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "Build",
"type": "shell",
"command": "g++ -g /home/danny/Documents/C++_Projects/24_-_Classes/main.cpp -o Classes",
"group": {
"kind": "build",
"isDefault": true
},
"problemMatcher":"$gcc"
}
]
}
Appreciate any help. And just in case you're wondering, the reason I don't just finish the tutorial in Codeblocks or VS Community is that I like to know what's going on under the hood in most things. Plus I'd like to get VS Code working for me as it's been great so far.
in tasks.json:
"label": "g++.exe build active file",
"args": [
"-g",
"${fileDirname}\\**.cpp",
//"${fileDirname}\\**.h",
"-o",
"${fileDirname}\\${fileBasenameNoExtension}.exe",
],
in launch.json:
"preLaunchTask": "g++.exe build active file"
it will work if your sources are in separated folder
feeling lazy,
This is tasks.json of vscode for linux distros, to compile multiple cpp files.
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "C/C++: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${fileDirname}/*.cpp",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "/usr/bin"
},
"problemMatcher": [
"$gcc"
],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
This is a Windows answer for the same problem:
I was struggling with this as well until I found the following answer at https://code.visualstudio.com/docs/cpp/config-mingw :
You can modify your tasks.json to build multiple C++ files by using an argument like "${workspaceFolder}\\*.cpp" instead of ${file}. This will build all .cpp files in >your current folder. You can also modify the output filename by replacing "${fileDirname}\\${fileBasenameNoExtension}.exe" with a hard-coded filename (for >example "${workspaceFolder}\\myProgram.exe").
Note that the F in workspaceFolder is capitalized.
As an example, in my tasks.json file in my project, the text in between the brackets under "args" originally appeared as follows:
"-g",
"${file}",
"-o",
"${fileDirname}\\${fileBasenameNoExtension}.exe"
This gave me reference errors because it was only compiling one and not both of my files.
However, I was able to get the program to work after changing that text to the following:
"-g",
"${workspaceFolder}\\*.cpp",
"-o",
"${fileDirname}\\${fileBasenameNoExtension}.exe"
If you have multiple files and one depends on a cpp file for another, you need to tell g++ to compile it as well, so the linker can find it. The simplest way would be:
$ g++ Cat.cpp main.cpp -o Classes
As a side note, you should probably compile with warnings, minimally -Wall, likely -Wextra, and possibly -Wpedantic, so you know if something you're doing is problematic.
After finding a lot of solutions I find this only working,
install the code runner extension. in settings,
go to open settings in the right upper corner
and simply paste this line in setting.json before the end of last closing bracket }
"code-runner.executorMap": {
"cpp": "cd $dir && g++ *.cpp -o $fileNameWithoutExt && $dir$fileNameWithoutExt",
},
[settings.json --> file looks like]
: https://i.stack.imgur.com/pUBYU.png
"tasks": [
{
"label": "echo",
"type": "shell",
"command": "g++",
"args":[
"-g","main.cpp","cat.cpp"
],
"group": {
"kind": "build",
"isDefault": true
}
}
Just add cat.cpp in args and then try to run. It should run without error on VS code
On Windows the solution is
{
"version": "2.0.0",
"tasks": [
{
"type": "cppbuild",
"label": "C/C++: cl.exe compila il file attivo",
"command": "cl.exe",
"args": [
"/Zi",
"/EHsc",
"/nologo",
"/Fe:",
"${fileDirname}\\${fileBasenameNoExtension}.exe",
"*.c"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": [
"$msCompile"
],
"group": {
"kind": "build",
"isDefault": true
},
"detail": "compilatore: cl.exe"
}
]
}
On the terminal tab of your VS Code program write the following:
$ g++ nameOne.cpp nameTwo.cpp -o a.out
$ ./a.out
For Mac you can use
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "shell: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"-Wall",
"-Wextra",
"-Wpedantic",
"${workspaceFolder}/*/*.cpp",
"${fileDirname}/*.cpp",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "/usr/bin"
},
"problemMatcher": [
"$gcc"
],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
This will compile all the cpp file with all the directories which contain .cpp files.
credits: Anns98.
Remember below args are belongs to g++.10.2.0 C++17.
You should tweak your compiler implicitly/explicitly to achieve the consistency you desire.
CHECKOUT:
winlibs (gcc-10.2.0-llvm-11.0.0-mingw-w64-8.0.0-r5) looks promising.
{
"version": "2.0.0",
"tasks": [
{
"type": "cppbuild",
"label": "retr0C++",
"command": "C:\\mingw64\\bin\\g++",
"args": [
"-std=c++17",
"-I",
"${fileDirname}\\includes",
"-o",
"${fileDirname}\\${fileBasenameNoExtension}.exe",
"-g",
//"${file}",
"${fileDirname}\\**.cpp"
],
"options": {
"cwd": "C:\\mingw64\\bin"
},
"problemMatcher": ["$gcc"],
"group": {
"kind": "build",
"isDefault": true
},
"detail": "compiler: C:\\mingw64\\bin\\g++"
}
]
}
As I understand, your program 24_-_Classes architecture just shows like:
24_-_Classes
|
|_.vscode
| |__c_cpp_properties.json
| |__launch.json
| |__settings.json
| |__tasks.json
|__cat.cpp
|__cat.h
|__main.cpp
Bro, I know what you mean "I understand that I may need to tell VS Code where to look for the Cat.cpp file but it's strange to me that it finds the header in the same location. ".
c_cpp_properties.json: allows you to change settings such as the path to
the compiler, include paths.
As your project architecture shows, your include file is located in the same directory of your source files.
So your c_cpp_properties.json should be looks like:
{
"configurations": [
{
"name": "Mac",
"includePath": [
// This is the include files directory
"${workspaceFolder}/**", // Have Change
"/Library/Developer/CommandLineTools/usr/include",
"/Library/Developer/CommandLineTools/usr/lib/clang/9.0.0/include",
"/usr/local/include",
"/Library/Developer/CommandLineTools/usr/include/c++/v1",
"/usr/include"
],
"defines": [],
"macFrameworkPath": [
"/System/Library/Frameworks",
"/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks",
"/Library/Frameworks"
],
"compilerPath": "/usr/bin/clang",
"cStandard": "c11",
"cppStandard": "c++11",
"intelliSenseMode": "clang-x64"
}
],
"version": 4
}
Notice that line ""${workspaceFolder}/**", // Have Change", as my
comment"// This is the include files directory" shows, change your
""${workspaceRoot}"," to my ""${workspaceFolder}/**".(This is used to add include file directory.)
Change this configuration to your needed Linux. E.g:
{
"configurations": [
{
"name": "Linux",
"includePath": [
// This line is to add include file directory.
"${workspaceFolder}/**" //Needed to Notices!
"/usr/include/c++/7",
"/usr/include/x86_64-linux-gnu/c++/7",
"/usr/include/c++/7/backward",
"/usr/lib/gcc/x86_64-linux-gnu/7/include",
"/usr/local/include",
"/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed",
"/usr/include/x86_64-linux-gnu",
"/usr/include",
],
"defines": [],
"compilerPath": "/usr/bin/gcc",
"cStandard": "c11",
"cppStandard": "c++17",
"intelliSenseMode": "clang-x64"
}
],
"version": 4
}
There is no need to add that lines:
"/home/danny/Documents/C++_Projects/24_-_Classes/Cat.cpp",
"/home/danny/Documents/C++_Projects/24_-_Classes/",
"/home/danny/Documents/C++_Projects/24_-_Classes/.vscode",
"/home/danny/Documents/C++_Projects/24_-_Classes/.vscode/Cat.cpp"
And I also know what your want to know"At one point I wondered if I need to add a double command in there to tell the compiler to build both .cpp files in the tasks.json",
Your tasks.json just looks like:
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "Compile With clang++",
//"command": "clang++",/usr/bin/clang++
"command": "/usr/bin/clang++",
"args": [
"-std=c++11",
"-stdlib=libc++",
// My project fitBodyBootCamp were under
// /Users/marryme/VSCode/CppProject/fitBodyBootCamp
// So ${workspcaeFolder} also were
// /Users/marryme/VSCode/CppProject/fitBodyBootCamp
// all the *.cpp files were under
// /Users/marryme/VSCode/CppProject/fitBodyBootCamp
"${workspaceFolder}/*.cpp", // Have changed
"-o",
// Thanks those chiense website bloggers!
// 1.mac vscode compile c++ multi-directory code demo
// https://blog.csdn.net/fangfengzhen115/article/details/121496770?utm_medium=distribute.pc_relevant.none-task-blog-2~default~baidujs_baidulandingword~default-4.pc_relevant_default&spm=1001.2101.3001.4242.3&utm_relevant_index=7
// 2.Compile and debug c++ multi-folder project under VSCode (non-makefile)
// https://blog.csdn.net/BaiRuichang/article/details/106463035
// I also put the main.o under my current workspace directory
// This after "-o" is the target file test.o or test.out or test
"${workspaceFolder}/${fileBasenameNoExtension}", // Have changed
"-I",
// This after "-I" if the include files directory
"${workspaceFolder}", // Have changed
"-Wall",
"-g"
],
"options": {
// "cwd" is the source files directory
"cwd": "${workspaceFolder}" // Have changed
},
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
That line I add a comment "//Have changed" that's what you need to notice.
Notices: your source files are not only, that are multiple sources.
So, just use using an argument like "${workspaceFolder}/*.cpp" instead of ${file}.
Also, just use using an argument like
"${workspaceFolder}/${fileBasenameNoExtension}" instead of "${fileDirname}/${fileBasenameNoExtension}".
Change this configuration to your needed Linux, e.g:
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${workspaceFolder}/*.cpp", // Need to change!
"-o",
"${workspaceFolder}/${fileBasenameNoExtension}" // Need to change!
],
"options": {
// If This not work, just change to ""cwd": "${workspaceFolder}""
"cwd": "/usr/bin" //I do not if change in Linux!
},
"problemMatcher": ["$gcc"],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
And your launch.json just looks like:
{
// 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": "Debug With LLDB",
"type": "lldb",
"request": "launch",
// "program" is the target file diretory
"program": "${workspaceFolder}/${fileBasenameNoExtension}", // Have changed
"args": [],
"stopAtEntry": true,
//"cwd": "${workspaceFolder}/../build",// Have changed
//"cwd": "${fileDirName}", ${workspaceFolder}/../build
// Changes the current working directory directive ("cwd") to the folder
// where main.cpp is.
// This "cwd" is the same as "cwd" in the tasks.json
// That's the source files directory
"cwd": "${workspaceFolder}", // Have changed
"environment": [],
"externalConsole": false,
"preLaunchTask": "Compile With clang++"
}
]
}
Change this configuration to your needed Linux, e.g:
{
"version": "0.2.0",
"configurations": [
{
"name": "g++ build and debug active file",
"type": "cppdbg",
"request": "launch",
// "program" is the target file diretory
"program": "${workspaceFolder}/${fileBasenameNoExtension}", // Have changed
"args": [],
"stopAtEntry": false,
// That's the source files directory
"cwd": "${workspaceFolder}", // Notices!!!
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
],
"preLaunchTask": "g++ build active file",
"miDebuggerPath": "/usr/bin/gdb"
}
]
}
If you are using Code-Runner to run your project, settings.json looks like:
{
"files.defaultLanguage": "c++",
"editor.suggest.snippetsPreventQuickSuggestions": false,
"editor.acceptSuggestionOnEnter": "off",
"code-runner.runInTerminal": true,
"code-runner.executorMap": {
// 0.Only One Simple C/C++ file build, compile, debug...
//"c": "cd $dir && gcc -std=c11 -stdlib=libc++ $fileName -o $fileNameWithoutExt && $dir$fileNameWithoutExt",
//"cpp": "cd $dir && g++ -std=c++11 -stdlib=libc++ $fileName -o $fileNameWithoutExt && $dir$fileNameWithoutExt"
//"c": "cd $dir && make && ./fileNameWithoutExt && make clean",
//"cpp": "cd $dir && make && ./fileNmaeWithoutExt && make clean"
// "c": "cd $dir && make main && ../build/main && make clean",
// "cpp": "cd $dir && make main && ../build/main && make clean"
// 1.0 Reference
// Thanks chinese website blogger!
// (Configure multiple c file compilation with vscode on Mac os)
// https://blog.csdn.net/songjun007/article/details/117641162
//"c": "cd $dir && gcc -std=c11 -stdlib=libc++ -I ${workspaceFolder}/inc ${workspaceFolder}/*.c -o ${workspaceFolder}/build/${fileBasenameNoExtension} && $dir$fileNameWithoutExt",
//"cpp": "cd $dir && g++ -std=c++11 -stdlib=libc++ -I ${workspaceFolder}/inc ${workspaceFolder}/*.cpp -o ${workspaceFolder}/build/${fileBasenameNoExtension} && $dir$fileNameWithoutExt"
// 1.1Use gcc or g++
// "c": "cd $dir && gcc -std=c11 -stdlib=libc++ $dir/../src/*.c -o $dir/../build/$fileNameWithoutExt && $dir/../build/$fileNameWithoutExt",
//"cpp": "cd $dir && g++ -std=c++11 -stdlib=libc++ $dir/../src/*.cpp -o $dir/../build/$fileNameWithoutExt && $dir/../build/$fileNameWithoutExt"
//
// clang -g /Users/marryme/VSCode/CppProject/fitBody/src/bank.cpp /Users/marryme/VSCode/CppProject/fitBody/src/main.cpp -o /Users/marryme/VSCode/CppProject/fitBody/build/main
// 1.2Use clang or clang++
//"c": "cd $dir && clang -std=c11 -stdlib=libc++ $dir/../src/*.c -o $dir/../build/$fileNameWithoutExt && $dir/../build/$fileNameWithoutExt",
//"cpp": "cd $dir && clang++ -std=c++11 -stdlib=libc++ $dir/../src/*.cpp -o $dir/../build/$fileNameWithoutExt && $dir/../build/$fileNameWithoutExt"
// 2.Seprated multiple sourece C/C++ files under different folder build, compile, debug...
// if put main.o and debug folder into new directory ./build/
//"c": "cd $dir && clang -std=c11 -stdlib=libc++ $dir/*.c -o $dir/../build/$fileNameWithoutExt && $dir/../build/$fileNameWithoutExt",
//"cpp": "cd $dir && clang++ -std=c++11 -stdlib=libc++ $dir/*.cpp -o $dir/../build/$fileNameWithoutExt && $dir/../build/$fileNameWithoutExt"
// 3.Mutiple sourece C/C++ files under same folder build, compile, debug...
// if put main.o and debug folder into the current directory "./"
"c": "cd $dir && clang -std=c11 -stdlib=libc++ $dir/*.c -o $dir/$fileNameWithoutExt && $dir/$fileNameWithoutExt", // Have changed
"cpp": "cd $dir && clang++ -std=c++11 -stdlib=libc++ $dir/*.cpp -o $dir/$fileNameWithoutExt && $dir/$fileNameWithoutExt" // Have changed
},
"code-runner.saveFileBeforeRun": true,
"code-runner.preserveFocus": false,
"code-runner.clearPreviousOutput": false,
"code-runner.ignoreSelection": true,
"C_Cpp.clang_format_sortIncludes": true,
"editor.formatOnType": true,
"clang.cxxflags": [
"-std=c++11"
],
"clang.cflags": [
"-std=c11"
],
"C_Cpp.updateChannel": "Insiders",
"[makefile]": {
"editor.insertSpaces": true
},
"C_Cpp.default.includePath": [
"${workspaceFolder}"
],
"clang.completion.enable": true
}
Change this configuration to your needed Linux, that may be like:
{
"files.defaultLanguage": "c++",
"editor.suggest.snippetsPreventQuickSuggestions": false,
"editor.acceptSuggestionOnEnter": "off",
"code-runner.runInTerminal": true,
"code-runner.executorMap": {
"c": "cd $dir && gcc -std=c11 -stdlib=libc++ $dir/*.c -o $dir/$fileNameWithoutExt && $dir/$fileNameWithoutExt", // Have changed
"cpp": "cd $dir && g++ -std=c++11 -stdlib=libc++ $dir/*.cpp -o $dir/$fileNameWithoutExt && $dir/$fileNameWithoutExt" // Have changed
},
"code-runner.saveFileBeforeRun": true,
"code-runner.preserveFocus": false,
"code-runner.clearPreviousOutput": false,
"code-runner.ignoreSelection": true,
"C_Cpp.clang_format_sortIncludes": true,
"editor.formatOnType": true,
"clang.cxxflags": [
"-std=c++11"
],
"clang.cflags": [
"-std=c11"
],
"C_Cpp.updateChannel": "Insiders",
"C_Cpp.default.includePath": [
"${workspaceFolder}"
],
"clang.completion.enable": true
}
But I suggest that you may read Using C++ on Linux in VS Code.
END.
Open your tasks.json file and put the following in it:
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "C/C++: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${workspaceFolder}/*.c",
"${workspaceFolder}/*.h",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "/usr/bin"
},
"problemMatcher": [
"$gcc"
],
"group": "build"
},
{
"type": "cppbuild",
"label": "C/C++: gcc-8 build active file",
"command": "/usr/bin/gcc-8",
"args": [
"-fdiagnostics-color=always",
"-g",
"${workspaceFolder}/*.c",
"${workspaceFolder}/*.h",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "${fileDirname}"
},
"problemMatcher": [
"$gcc"
],
"group": {
"kind": "build",
"isDefault": true
},
"detail": "Task generated by Debugger."
}
]
}
If you have any C++ source, add "${workspaceFolder}/*.cpp" too.
Note that if you haven't any of those files in your dir it gives you an error.
If you are using linux then know how to use make. If save a lot of time and effort. If you have even 10s or 100s of files and some dependencies are there then just make a Makefile once and every time you compile just use one command make and that will do all the work for you. Even you can make a keyboard shortcut for that command in VSCode.
Check out here to use make and here for using that in VSCode.
I had similar problem, and it was not easy to find answer which I fully understand. First thing you need to understand is that all .cpp files used in your project need to be compiled for the linker. for project with one .cpp file there is relatively no issue. you simply need to tell g++ which .cpp file need to be compiled by running the following command in the terminal from the root directory:
g++ -g main.cpp -o mainApp
This tells g++ to compile main.cpp an create a consolApp (output file) named mainApp.
In the case of a project with more than one .cpp file,
|--root
|--main.cpp}
|--include1
|-- foo1.h
|-- foo1.cpp
|-- include2
|-- foo2.h
|-- foo2.cpp
|-- foo3.cpp
To compile this project and build the output file we run this in the terminal:
g++ -g main.cpp include1/foo1.cpp include2/foo2.cpp foo3.cpp -o mainApp
Note that the order in which we pass the .cpp files to be compiled doesn't really matter.
You can already understand that for a very large project writing that command will be very tedious. you can rewrite is as follow
g++ -g ./*.cpp include1/*.cpp include2/*.cpp -o mainApp
This simply tells g++ to compile all .cpp file in the root, include1 and include2 folders.
What if your project has a lot of folders, you can simply run it recursively
g++ -g ./**/*.cpp -o mainApp
This is kind of telling g++ to go through root folder and through other folder and compile all .cpp files it will find.
To do the same thing in vscode, go to the tasks.json file, and in 'args' add :
"${workspaceFolder}/.cpp",
"${workspaceFolder}/**/.cpp",
This is the equivalent of :
g++ -g ./**/*.cpp -o mainApp
I had trouble to getting VS Code to compile multiple source files. It turned out to be that the workspace folder file path had a folder with a space in it. That space would cause the changed line to be read literally instead of looking for all .cpp files. I changed the path to have no spaces, and then it compiled successfully.
I only had to change one line in the tasks.json file:
{
"version": "2.0.0",
"tasks": [
{
"type": "cppbuild",
"label": "C/C++: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-fdiagnostics-color=always",
"-g",
"${workspaceFolder}/*.cpp", //changed line from "${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "${fileDirname}"
},
"problemMatcher": [
"$gcc"
],
"group": "build",
"detail": "compiler: /usr/bin/g++"
}
]
}
'Adds single quotes'
I also had this problem on linux, and arrived at this solution based on some other answers and comments here.
Replacing the args parameter "${file}" in tasks.json with "${fileDirname}/*.cpp" will work for some of us - but only if there are no spaces in the resulting path string.
However, I have spaces in some of the directory names on the path to my working directory. So, when I use ${fileDirname} to get the directory string, there are spaces in the result.
The presence of spaces means this argument will automatically be surrounded in double quotes, becoming a literal string and also destroying our expected behaviour of the asterisk wildcard *. The compiler will simply be looking for a single file named *.cpp in that directory.
A set of single quotes around the relevant portion of the argument solves the problem (and I won't need to go removing all the spaces from my existing directory names).
And so: the argument "${fileDirname}/*.cpp" gains some single quotes and becomes "'${fileDirname}'/*.cpp" and everything works as expected.
tasks.json
{
"tasks": [
{
"type": "cppbuild",
"label": "C/C++: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"'${fileDirname}'/*.cpp", // note the placement of the single quotes
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
// ... other json blocks ...
}
]
}
For those who are struggling with not working syntax like ${workspaceFolder}\**.cpp, ${workspaceFolder}/**.cpp, ${workspaceFolder}/*.cpp, etc., be sure to check also other parameters in tasks.json.
On my ArchLinux with VS Code 1.74.2, setting "type": "cppbuild" helped. So, my tasks.json looks like this:
{
"version": "2.0.0",
"tasks": [
{
// "type": "cppbuild", // Not working if commented out
"type": "cppbuild", // OK
"label": "Build with Clang++ (Linux)",
"command": "clang++",
"args": [
"-std=c++17",
"${fileDirname}/*.cpp",
"-o",
"${fileDirname}/${fileBasenameNoExtension}",
],
"options": {
"cwd": "${fileDirname}"
},
"group": {
"kind": "build",
"isDefault": true
},
},
]
}
It seems that VS Code wraps arguments in quotes for several reasons, also mentioned by others.
Related
I unsuccessfully was looking 2 days on google to find a clear paragraph to describe how to include dynamic libraries (files with .dylib extension on Mac iOS) in order to be compiled by clang++ when someone is setting up the task.json and/or c_cpp_properties.json files - (prior to press F5 in order to launch the task and execute the source code)
Particularly I would like to include next two .dylib files:
/usr/local/Cellar/glfw/3.3.3/lib/libglfw.3.3.dylib;
/usr/local/Cellar/glew/2.2.0_1/lib/libGLEW.2.2.0.dylib;
Have to mention that I successfully succeeded to make the clang++ to compile in the OpenGL main.cpp file both glew.h and glfw3.h headers as per the following snippet:
// GLEW
#define GLEW_STATIC
#include <GL/glew.h>
// GLFW
#include <GLFW/glfw3.h>
...
This task was accomplished writing the next c_cpp_properties.json file:
{
"configurations": [
{
"name": "Mac",
"includePath": [
"${workspaceFolder}/**",
"${workspaceFolder}/include"
],
"defines": [],
"macFrameworkPath": [
"/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks"
],
"compilerPath": "/usr/bin/clang++",
"cStandard": "gnu17",
"cppStandard": "gnu++14",
"intelliSenseMode": "macos-gcc-x64"
}
],
"version": 4
}
where the magic is done by "macFrameworkPath" instruction.
But yet is not enough.
I still have this error when the clang++ compiles:
clang: error: linker command failed with exit code 1 (use -v to see invocation).
And this - as I understood after googling the solution - happens because is necessary to include those two dynamic libraries which I mentioned earlier.
But as I said in the beginning I didn't find how to do it.
Maybe someone can come up with a clear and appropriate solution.
My best guess is to add a new argument in task.json script, which by the way looks like that:
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "clang++ build active file",
"command": "/usr/bin/clang++",
"args": [
"-std=c++17",
"-stdlib=libc++",
"-g",
"${file}",
"-I/Users/Armonicus/MyProjects/C++VSCodeProjects/projects/helloworld01/include",
"-o",
"${fileDirname}/src/${fileBasenameNoExtension}",
"-Wno-deprecated",
"-Wno-pragma-once-outside-header"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": ["$gcc"],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
Best regards to all readers.
It seems you are indeed need to pass the libs into arguments of clang++.
Try to do this with -l flag, pointing to target library.
Add
"-l /usr/local/Cellar/glfw/3.3.3/lib/libglfw.3.3.dylib"
and
"-l /usr/local/Cellar/glew/2.2.0_1/lib/libGLEW.2.2.0.dylib" to the args list of strings.
The solution to this particular problem is to add in task.json the next command arguments:
task.json
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "clang++ build active file",
"command": "/usr/bin/clang++",
"args": [
"-std=c++17",
"-stdlib=libc++",
"-g",
"${file}",
"-I/Users/Armonicus/MyProjects/C++VSCodeProjects/projects/helloworld01/include",
"/usr/local/Cellar/glfw/3.3.3/lib/libglfw.3.3.dylib",
"/usr/local/Cellar/glew/2.2.0_1/lib/libGLEW.2.2.0.dylib",
"-o",
"${fileDirname}/src/${fileBasenameNoExtension}",
"-Wno-deprecated",
"-Wno-pragma-once-outside-header"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": ["$gcc"],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
As everyone can see, simply writing the full path of the file as additional argument will be accepted by compiler
I've installed OpenCV On Ubuntu successfully and I managed to run a sample code as:
g++ main.cpp -o testoutput -std=c++11 `pkg-config --cflags --libs opencv`
I've tried to run it with Visual Studio Code, I've installed the extension of C/C++ and code runner and ran it with the following configuration:
tasks.json:
{
"tasks": [
{
"type": "cppbuild",
"label": "C/C++: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}",
"-std=c++11","`pkg-config","--cflags","--libs opencv`"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": [
"$gcc"
],
"group": {
"kind": "build",
"isDefault": true
},
"detail": "Task generated by Debugger."
}
],
"version": "2.0.0"
}
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++ - Build and debug active file",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}/${fileBasenameNoExtension}",
"args": ["-std=c++11","`pkg-config","--cflags","--libs opencv`"],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
],
"preLaunchTask": "C/C++: g++ build active file",
"miDebuggerPath": "/usr/bin/gdb"
}
]
}
I got the following error:
[Running] cd "/home/kfir/code/opencv_test/" && g++ main.cpp -o main && "/home/kfir/code/opencv_test/"main
main.cpp:1:10: fatal error: opencv2/core.hpp: No such file or directory
#include <opencv2/core.hpp>
^~~~~~~~~~~~~~~~~~
compilation terminated.
[Done] exited with code=1 in 0.032 seconds
Note: I'm using VSCode on mac and connect Ubuntu remote machine by ssh, the terminal works fine with the command of g++ above
Be sure to add the location to openCV header files in your includePath.
c_cpp_properties.json file :
{
"configurations": [
{
"name": "Linux",
"includePath": [
"${default}",
"~/opencv4.5-custom/include/opencv4"
],
"defines": [],
"compilerPath": "/usr/bin/gcc",
"cStandard": "gnu17",
"cppStandard": "gnu++14",
"intelliSenseMode": "gcc-x64"
}
],
"version": 4
}
Mine says "~/opencv4.5-custom/include/opencv4" but it could be "/usr/include/opencv4" or something else, depending on how and where you installed openCV.
You also need to modify task.json to add the arguments to the compiler as given by the pkg-config --cflags --libs opencv4 command, if you would run it in the terminal. You'll need to give the path to the shared object files.
Here's the content of my task.json file :
{
"tasks": [
{
"type": "cppbuild",
"label": "C/C++: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}",
"-I", "~/opencv4.5-custom/include/opencv4",
"-L", "~/opencv4.5-custom/lib",
"-l", "opencv_core",
"-l", "opencv_videoio",
"-l", "opencv_imgproc",
"-l", "opencv_highgui"
],
"options": {
"cwd": "${workspaceFolder}"
},
"problemMatcher": [
"$gcc"
],
"group": {
"kind": "build",
"isDefault": true
},
"detail": "Task generated by Debugger."
}
],
"version": "2.0.0"
}
You'll also need the change the paths depending to you setup.
Here I have only included the modules that are used by my program (with the lines "-l", "opencv_core" and so on...) so add or remove modules according to your needs.
I am on Ubuntu 20.04 using Vscode.
I'm trying to compile files got here
Dialog Box
I type this in a terminal
g++ main.cpp examplewindow.cpp -o WindowBox11 -v -std=c++0x `pkg-config gtkmm-3.0 --cflags --libs`
and it compiles fine.
But doesn't work with Vscode.
This is my c_cpp_properties.json file
{
"configurations": [
{
"name": "Linux",
"includePath": [
"${workspaceFolder}/**",
"/usr/include/gtkmm-3.0",
"/usr/include/**"
],
"defines": [],
"compilerPath": "/usr/bin/g++",
"cStandard": "gnu18",
"cppStandard": "gnu++14",
"intelliSenseMode": "gcc-x64",
"compilerArgs": [
"-std=c++0x",
"`pkg-config gtkmm-3.0 --cflags --libs`",
"-v"
]
}
],
"version": 4
}
and tasks.json file
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "build & run", //It's name of the task , you can have several tasks
"type": "shell", //type can be either 'shell' or 'process' , more details will be given below
"command": "g++",
"args": [
"-g", //gnu debugging flag , only necessary if you want to perform debugging on file
"${file}", //${file} gives full path of the file
"-o",
"${workspaceFolder}\\build\\${fileBasenameNoExtension}", //output file name
"&&", //to join building and running of the file
"${workspaceFolder}\\build\\${fileBasenameNoExtension}",
],
"group": {
"kind": "build", //defines to which group the task belongs
"isDefault": true
},
"presentation": { //Explained in detail below
"echo": false,
"reveal": "always",
"focus": true,
"panel": "shared",
"clear": false,
"showReuseMessage": false
},
"problemMatcher": "$gcc"
},
]
}
Compiling with Vscode i got these errors
Any ideas what to ?
I suspect that the problem is with pkg-config in compilerArgs.
Try to separate each argument:
"`pkg-config", "gtkmm-3.0", "--cflags", "--libs`"
After many tries
got solution from
Variables Reference
c_cpp_properties.json reference
and Using C++ on Linux in VS Code
First I put all files in same folder (in my case .cc and .h).
To compile in command line I use
g++ main.cc examplewindow.cc -o Dialogue_windo11 -std=c++0x `pkg-config gtkmm-3.0 --cflags --libs`
You must reproduce this command in vscode
c_cpp_properties.json
{
"env": {
"myDefaultIncludePath": ["${workspaceFolder}", "${workspaceFolder}/include"],
"myCompilerPath": "/usr/bin/g++"
},
"configurations": [
{
"name": "Linux",
"intelliSenseMode": "gcc-x64",
"includePath": ["${myDefaultIncludePath}", "/usr/include/**"],
"compilerPath": "/usr/bin",
"cStandard": "gnu18",
"cppStandard": "gnu++14",
"compilerArgs": [
"-v"
]
}
],
"version" : 4
}
and tasks.json
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "g++ build active file",
"type": "shell",
"command": "/usr/bin/g++",
"args": [
"${fileDirname}/*.cc", //to compile all .cc files
"-o",
"${fileDirname}/MessageBox",
"-std=c++0x",
"`pkg-config", "gtkmm-3.0", "--cflags", "--libs`"
],
"problemMatcher": [],
"group": {
"kind": "build",
"isDefault": true
}
}
]
}
I'm using VSCode to create a C++ project and keep getting this error when trying to build && debug. When running from console if I use 'g++ -o main 'main.cpp' 'file_1.cpp' 'file_2.cpp'' it works and compiles correctly.
I have read that this is something to do with the linking of files? Does anyone know how to fix this in VSCode? I have a default launch.json configuration file that builds the active file if this helps.
Here is the contents of my tasks.json file:
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "shell: g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "/usr/bin"
},
"problemMatcher": [
"$gcc"
],
"group": {
"kind": "build",
"isDefault": true
}
},
{
"type": "shell",
"label": "g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "/usr/bin"
}
}
]
}
EDIT: I'm using Debian 10 'Buster'
Many thanks
You need to modify tasks.json for compile all .cpp .
In args change ${file} for ${workspaceFolder}/*.cpp
To run the build task press Ctrl+Shift+B, this generate a execution file in the current directory. Execute this file in the terminal for run the program (./fileName)
I am trying to learn C++, but I am unable to get any code running.
#include <iostream>
int main()
{
std::cout << "Hello world!";
return 0;
}
When I run this(or another file), it creates a different unrecognized file. (https://imgur.com/a/07rpngl, picture 2) Then it gives the error at picture 1.
This is the 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": "cpp - Build and debug active file",
"type": "cppdbg",
"request": "launch",
"program": "${fileDirname}/${fileBasenameNoExtension}",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "gdb",
"setupCommands": [
{
"description": "Enable pretty-printing for gdb",
"text": "-enable-pretty-printing",
"ignoreFailures": true
}
],
"preLaunchTask": "cpp build active file",
"miDebuggerPath": "/usr/bin/gdb"
}
]
}
And this is the task file:
{
"version": "2.0.0",
"tasks": [
{
"type": "shell",
"label": "g++ build active file",
"command": "/usr/bin/g++",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "/usr/bin"
},
"problemMatcher": [
"$gcc"
],
"group": "build"
},
{
"type": "shell",
"label": "cpp build active file",
"command": "/usr/bin/cpp",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "/usr/bin"
},
"problemMatcher": [
"$gcc"
],
"group": "build"
},
{
"type": "shell",
"label": "clang++ build active file",
"command": "/usr/bin/clang++",
"args": [
"-g",
"${file}",
"-o",
"${fileDirname}/${fileBasenameNoExtension}"
],
"options": {
"cwd": "/usr/bin"
},
"problemMatcher": [
"$gcc"
],
"group": "build"
}
]
}
The settings.json file is empty.
Both running without debugging and with it gives the same error. How can I fix this?
Ways that were tried:
1) Tried restarting both the application and the computer, doesn't work.
2) Tried using terminal to compile, run and debug the code. It works, but is there a way to do this over VS Code? (Should I open another question just for VS Code?)
# First, change your directory to the one that you want to use
# Run the following to compile in the same directory:
g++ -Wall -Wextra -pedantic -Wshadow -std=c++11 -g -o nameforexe source.cpp
# Change -std=c++11 to whatever version of c++ you want to use, and also the file names.
# To run it after this normally do this:
./nameforexe
# To debug, do:
gdb ./nameforexe
# After gdb opens, write "run" without " to run the file.
# If there is a problem, it will tell you. If there isn't it will run normally.
Thanks to David C. Rankin for this. There is more info in the comments for this question.
3) Using CMake(suggested by dboy). I wasn't able to do this. After it says generated in the output section, I wasn't able to find the file to run the HelloWorld application. (Image 3 shows the files)
The CMakeLists.txt file:
cmake_minimum_required(VERSION 3.10.2)
project("HelloWorld")
set(SOURCE Helloworld.cpp)
add_executable("HelloWorldBuild" HelloWorld.cpp)
It didn't show any problems while compiling. CMake might be to advanced for me for now.