我的博客→TanJX的自留地html
我这个配置方法反正在win10上是能够用的,我本身的笔记本就是win10的系统。可是在实验室蹭的学长的主机倒是win7的系统,按道理来讲这个配置应该是不分系统的?可是我确实是折腾了好几天,看了不少博客的配置方法,也问过稍微会一些的人,没有一个能解决我问题的,也但愿有人能评论解决个人问题,个人vscode问题是c++只能编译运行没法debug。每次按F5都是一闪而过,没法调试,再按就显示调试程序正在运行。-------2019.5.3
实验室我把系统换了,用了本身喜欢好久的ubuntu 18.04前端
虽然平时比赛要求用的是code blocks,可是很尴尬的是我不喜欢code blocks的那个界面,平时编程感受太白很伤眼睛。再加上最近一直在折腾我的博客,对于前端,虽然没基础,可是仍是知道用vs code还不错。所以,我又开始了瞎折腾的精神。但愿平时编程也能经过vs code编译c++,可是正常状况下vs code对c++编译是很不友好的。因此想要成功编译c++程序,要经过本身配置。可是我在网上搜到的教程不多有能一次解决个人问题的。因此参考了几篇博客后,总结了一下。ios
不须要更改,或者只是为了编译运行C/C++的能够直接往下看。
这个是Linux的,若是须要windows,能够本身试一试,具体应该不会差太多
由于文件分配不够美观(我用的文件比较多,致使生成的.o文件都堆叠在一块儿,很丑),因此我动了在编译文件时将生成的a/a.o文件更换位置再运行,一开始打算经过命令行命令直接在其余位置生成生成文件,可是我并无找到此类命令,而后发现编译时运行的命令是这样的cd "/home/acm/Documents/acm/" && g++ A.cpp -o A && "/home/acm/Documents/acm/"A
。因此我决定在编译后的命令间加上移动文件命令mv A /home/acm/Documents/acm/Documents/
这样的话就将生成文件放在了acm目录下的Documents文件夹下,不会致使多个a/a.o文件堆积在acm目录下。而task.json文件我没有找的修改方法,应该能够修改"command"实现,它能够运行脚本,可是我写不来。。。因此我是经过修改了code-runner的命令来实现的。下图为我修改后的vs code
实现方法
安装code-runner后在settings.json中找到code-runner.executorMap,将其中的cpp
修改成"cpp": "cd $dir && g++ $fileName -o $fileNameWithoutExt && mv $fileNameWithoutExt $dir/Documents/$fileNameWithoutExt && $dir/Documents/$fileNameWithoutExt",
其中的Documents是我本身的目录,请本身修改,其余编译命令也能够修改
我整个文件的结构如图
上面是正常的编译运行,还要一处就是调试的生成文件,这里修改launch.json便可
更改位置的task.jsonc++
{ // See https://go.microsoft.com/fwlink/?LinkId=733558 // for the documentation about the tasks.json format "version": "2.0.0", "command": "g++", "args": [ "-g", "-std=c++11", // "${workspaceFolder}/${file}", // "${file}", "${workspaceFolder}/${fileBasenameNoExtension}.cpp", "-o", "${workspaceFolder}/Documents/${fileBasenameNoExtension}.o", ],// 编译命令参数 "problemMatcher":{ "owner": "cpp", "fileLocation":[ "relative", "${workspaceFolder}/Documents" ], "pattern":[ { "regexp": "^([^\\\\s].*)\\\\((\\\\d+,\\\\d+)\\\\):\\\\s*(.*)$", "file": 1, "location": 2, //"message": 3 } ] }, "group": { "kind": "build", "isDefault": true } } //"command": "g++",
launch.jsonweb
{ // 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": "(gdb) Launch", "type": "cppdbg", "request": "launch", "program": "${workspaceFolder}/Documents/${fileBasenameNoExtension}.o", "args": [], "stopAtEntry": false, "cwd": "${workspaceFolder}/Documents", "environment": [], "externalConsole": false, "MIMode": "gdb", "miDebuggerPath": "/usr/bin/gdb", "preLaunchTask": "g++", "setupCommands": [ { "description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true } ] }, ] } //"program": "${workspaceFolder}/${fileBasenameNoExtension}.o", //"cwd": "${workspaceFolder}",
由于最近有人问我三个文件里的c_cpp_properties.json会报错,我也不知道报错的具体缘由,多是由于版本更新?几个月前vscode就能够配置时不须要在加c_cpp_properties.json这个文件了。对其他两个文件单独更新一下。也由于最近重装过电脑,本身从新找教程配置了一遍。
tasks.jsonshell
{ "version": "2.0.0", "tasks": [ { "label": "Build", "command": "g++", "args": [ "-g", "-Wall", "-std=c++11", "-lm", "${file}", "-o", "${fileDirname}/${fileBasenameNoExtension}.exe" ], "presentation": { "reveal": "always", "echo": false, "focus": true }, "problemMatcher": { "owner": "cpp", "fileLocation": "absolute", "pattern": { "regexp": "^(.*):(\\d+):(\\d+):\\s+(error):\\s+(.*)$", "file": 1, "line": 2, "column": 3, "severity": 4, "message": 5 } } }, { "label": "Run", "type": "shell", "dependsOn": "Build", "command": "${fileDirname}/${fileBasenameNoExtension}.exe", "args": [], "presentation": { "reveal": "always", "focus": true }, "problemMatcher": [], "group": { "kind": "test", "isDefault": true } } ] }
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": "(gdb) Launch", "type": "cppdbg", "request": "launch", "program": "${fileDirname}/${fileBasenameNoExtension}.exe", "args": [], "stopAtEntry": false, "cwd": "${workspaceFolder}", "externalConsole": false, //强调一下,我习惯用vscode自带的终端,因此你不习惯能够改成true "MIMode": "gdb", "miDebuggerPath": "E:\\vs code\\MinGW\\mingw64\\bin\\gdb.exe", "setupCommands": [ { "description": "Enable pretty-printing for gdb", "text": "-enable-pretty-printing", "ignoreFailures": true } ], "preLaunchTask": "Build" } ] }
Visual Studio Code (vscode)编译C++
整理:Visual Studio Code (vscode) 配置C、C++环境/编写运行C、C++(Windows)json
下载地址ubuntu
能够选择ctrl+shift+x在商店里搜索或者选择ctrl+shift+p打开命令框输入windows
ext install cpptools
安装该插件
听说MinGW已经不更新了?=.=因此安装MinGW-W64
安装过程请注意本身的电脑是32仍是64位的,其余的默认就能够了。还要额外注意下本身的下载地址后面要用。
而后打开个人电脑->属性->高级系统设置->环境变量
选择新建,添加刚刚记住的E:\vs code\mingw\mingw64\bin肯定后退出,注意这个应该是你本身的安装地址
检查一下本身是否安装配置完成
打开命令提示符输入
gcc -v
找一个文件夹做为你的工做区,而后在这个工做区下创建一个新的文件夹,命名为.vscode
,注意点是不能缺乏的。而后在你创建的.vscode
文件夹下创建三个.json
文件,分别为tasks.json,launch.json,c_cpp_properties.json。
配置内容以下:
tasks.json
{ "version": "2.0.0", "command": "g++", "args": ["-g","-std=c++11","${file}","-o","${workspaceRoot}\\${fileBasename}.exe"], "problemMatcher": { "owner": "cpp", "fileLocation": ["relative", "${workspaceRoot}"], "pattern": { "regexp": "^(.*):(\\d+):(\\d+):\\s+(warning|error):\\s+(.*)$", "file": 1, "line": 2, "column": 3, "severity": 4, "message": 5 } } }
launch.json
{ "version": "0.2.0", "configurations": [ { "name": "C++ Launch (GDB)", "type": "cppdbg", "request": "launch", "targetArchitecture": "x86", "program": "${workspaceRoot}\\${fileBasename}.exe", "miDebuggerPath":"E:/vs code/mingw/mingw64/bin/gdb.exe", "args": [], "stopAtEntry": false, "cwd": "${workspaceRoot}", "externalConsole": true, "preLaunchTask": "g++" } ] }
c_cpp_properties.json
{ "configurations": [ { "name": "Win32", "includePath": [ "${workspaceRoot}", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/x86_64-w64-mingw32", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/backward", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/tr1", "E:/vs code/mingw/mingw64/x86_64-w64-mingw32/include" ], "defines": [ "_DEBUG", "UNICODE", "__GNUC__=6", "__cdecl=__attribute__((__cdecl__))" ], "intelliSenseMode": "msvc-x64", "browse": { "path": [ "${workspaceRoot}", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/x86_64-w64-mingw32", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/backward", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include", "E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++/tr1", "E:/vs code/mingw/mingw64/x86_64-w64-mingw32/include" ] }, "limitSymbolsToIncludedHeaders": true, "databaseFilename": "", "compilerPath": "E:\\vs code\\mingw\\mingw64\\bin\\gcc.exe", "cStandard": "c11", "cppStandard": "c++17" } ], "version": 4 }
其中尤其须要注意的就是那些安装位置,配置的时候请参考个人来找到你本身安装的位置。
还有就是在一些地址输入不能用\
分割要用/
或者\\
例如:E:/vs code/mingw/mingw64/lib/gcc/x86_64-w64-mingw32/8.1.0/include/c++
E:/vs code/mingw是我安装时本身选的文件夹,从mingw64开始均为安装时本身出现的文件,因此请不要直接复制粘贴,注意本身的安装位置。
这样基本就配置完了,测试一下经典的Hello World
#include<iostream> using namespace std; int main() { cout<<"Hello World!"<<endl; return 0; }
直接F6运行,或者选择在return 0处加个断点再F5,都能成功测试是否配置完成。不过加断点输出的那个会比较好看=.=
固然估计在配置过程当中问题是少不了的。若是有我未提到的问题,你能够发给我邮件tanjinxiao25@gmail.com,我推荐你直接在GitHub的仓库里添加issue。由于我不能保证本身可以完全的解决,可是在issues里总有大佬会回答问题的。