Cài đặt visual studio code lập trình c++ dễ như ăn kẹo

-
Configure VS Code for Microsoft C++PrerequisitesCreate Hello WorldBuild helloworld.cppDebug helloworld.cppC/C++ configurationsTroubleshooting
Configure VS Code for Microsoft C++In this tutorial, you configure Visual Studio Code lớn use the Microsoft Visual C++ compiler and debugger on Windows.

Bạn đang xem: Cài đặt visual studio code lập trình c++ dễ như ăn kẹo

After configuring VS Code, you will compile and debug a simple Hello World program in VS Code. This tutorial does not teach you details about the Microsoft C++ toolset or the C++ language. For those subjects, there are many good resources available on the Website.

If you have any problems, feel free to file an issue for this tutorial in the VS Code documentation repository.

Prerequisites

To successfully complete this tutorial, you must do the following:

Install Visual Studio Code.

Install the C/C++ extension for VS Code. You can install the C/C++ extension by searching for ‘c++’ in the Extensions view (⇧⌘X (Windows, Linux Ctrl+Shift+X)).

*

Install the Microsoft Visual C++ (MSVC) compiler toolset.

If you have a recent version of Visual Studio, open the Visual Studio Installer from the Windows Start thực đơn và verify that the C++ workload is checked. If it’s not installed, then test the box & select the Modify button in the installer.

You can also install the Desktop development with C++ workload without a full Visual Studio IDE installation. From the Visual Studio Downloads page, scroll down until you see Tools for Visual Studio 2019 under the All Downloads section & select the tải về for Build Tools for Visual Studio 2019.

*

This will launch the Visual Studio Installer, which will bring up a dialog showing the available Visual Studio Build Tools workloads. Chạy thử the Desktop development with C++ workload and select Install.

*

Note: You can use the C++ toolset from Visual Studio Build Tools along with Visual Studio Code lớn compile, build, và verify any C++ codebase as long as you also have a valid Visual Studio license (either Community, Pro, or Enterprise) that you are actively using to lớn develop that C++ codebase.

Test your Microsoft Visual C++ installation

To use MSVC from a command line or VS Code, you must run from a Developer Command Prompt for Visual Studio. An ordinary shell such as PowerShell, Bash, or the Windows command prompt does not have the necessary path environment variables set.

To xuất hiện the Developer Command Prompt for VS, start typing ‘developer’ in the Windows Start thực đơn, và you should see it appear in the menu of suggestions. The exact name depends on which version of Visual Studio or the Visual Studio Build Tools you have installed. Select the tòa tháp to xuất hiện the prompt.

*

*

If the Developer Command Prompt is using the BuildTools location as the starting directory (you wouldn’t want to lớn put projects there), navigate lớn your user thư mục (C:usersyour username) before you start creating new projects.

Note: If for some reason you can’t run VS Code from a Developer Command Prompt, you can find a workaround for building C++ projects with VS Code in Run VS Code outside a Developer Command Prompt.

Create Hello World

From the Developer Command Prompt, create an empty thư mục called “projects” where you can store all your VS Code projects, then create a subfolder called “helloworld”, navigate into it, and mở cửa VS Code (code) in that thư mục (.) by entering the following commands:

mkdir projects

cd projects

mkdir helloworld

cd helloworld

code .

The “code .” command opens VS Code in the current working folder, which becomes your “workspace”. As you go through the tutorial, you will see three files created in a .vscode thư mục in the workspace:

tasks.json (build instructions)launch.json (debugger settings)c_cpp_properties.json (compiler path and IntelliSense settings)

Add a source code file

In the tệp tin Explorer title bar, select the New File button and name the file helloworld.cpp.

*

Add hello world source code

Now paste in this source code:

#include

Now press ⌘S (Windows, Linux Ctrl+S) lớn save the file. Notice how the file you just added appears in the File Explorer view (⇧⌘E (Windows, Linux Ctrl+Shift+E)) in the side bar of VS Code:


*

You can also enable auto Save khổng lồ automatically save your tệp tin changes, by checking Tự rượu cồn Save in the main File thực đơn.

The Activity Bar on the far left lets you xuất hiện different views such as Tìm kiếm, Source Control, & Run. You’ll look at the Run view later in this tutorial. You can find out more about the other views in the VS Code User Interface documentation.

Note: When you save or open a C++ file, you may see a notification from the C/C++ extension about the availability of an Insiders version, which lets you thử nghiệm new features & fixes. You can ignore this notification by selecting the X (Clear Notification).

Explore IntelliSense

In your new helloworld.cpp file, hover over vector or string khổng lồ see type information. After the declaration of the msg variable, start typing msg. As you would when calling a thành viên function. You should immediately see a completion danh sách that shows all the member functions, and a window that shows the type information for the msg object:

*

You can press the Tab key khổng lồ insert the selected thành viên; then, when you địa chỉ the opening parenthesis, you will see information about any arguments that the function requires.

Build helloworld.cpp

Next, you will create a tasks.json tệp tin to tell VS Code how to build (compile) the program. This task will invoke the Microsoft C++ compiler to create an executable file based on the source code.

From the main thực đơn, choose Terminal > Configure default Build Task. In the dropdown, which will display a tasks dropdown listing various predefined build tasks for C++ compilers. Choose cl.exe build active file, which will build the file that is currently displayed (active) in the editor.

*

This will create a tasks.json file in a .vscode thư mục and xuất hiện it in the editor.

Your new tasks.json tệp tin should look similar to lớn the JSON below:

"version"

:

"2.0.0"

,

"tasks"

: <

"type"

:

"shell"

,

"label"

:

"cl.exe build active file"

,

"command"

:

"cl.exe"

,

"args"

: <

"/Zi"

,

"/EHsc"

,

"/Fe:"

,

"$fileDirname

$fileBasenameNoExtension.exe"

,

"$file"

>,

"problemMatcher"

: <

"$msCompile"

>,

"group"

:

"kind"

:

"build"

,

"isDefault"

:

true

>

The command setting specifies the program to lớn run; in this case that is “cl.exe”. The args array specifies the command-line arguments that will be passed to cl.exe. These arguments must be specified in the order expected by the compiler. This task tells the C++ compiler to take the active file ($file), compile it, và create an executable tệp tin (/Fe: switch) in the current directory ($fileDirname) with the same name as the active file but with the .exe extension ($fileBasenameNoExtension.exe), resulting in helloworld.exe for our example.

Note: You can learn more about tasks.json variables in the variables reference.

The label value is what you will see in the tasks list; you can name this whatever you like.

The problemMatcher value selects the output parser lớn use for finding errors & warnings in the compiler output. For cl.exe, you’ll get the best results if you use the $msCompile problem matcher.

The "isDefault": true value in the group object specifies that this task will be run when you press ⇧⌘B (Windows, Linux Ctrl+Shift+B). This property is for convenience only; if you phối it to lớn false, you can still run it from the Terminal thực solo with Tasks: Run Build Task.

Running the build

Go back khổng lồ helloworld.cpp. Your task builds the active file and you want khổng lồ build helloworld.cpp.

To run the build task defined in tasks.json, press ⇧⌘B (Windows, Linux Ctrl+Shift+B) or from the Terminal main thực đối kháng choose Tasks: Run Build Task.

When the task starts, you should see the Integrated Terminal panel appear below the source code editor. After the task completes, the terminal shows output from the compiler that indicates whether the build succeeded or failed. For a successful C++ build, the đầu ra looks something lượt thích this:

*

Create a new terminal using the + button & you’ll have a new terminal (running PowerShell) with the helloworld thư mục as the working directory. Run ls and you should now see the executable helloworld.exe along with various intermediate C++ output và debugging files (helloworld.obj, helloworld.pdb).

*

You can run helloworld in the terminal by typing .helloworld.exe.

Note: You might need lớn press Enter a couple of times initially lớn see the PowerShell prompt in the terminal. This issue should be fixed in a future release of Windows.

Xem thêm: Đồng Hồ Cơ Sai Số Cho Phép Của Đồng Hồ Cơ, Kiểm Tra Độ Chính Xác Của Đồng Hồ Cơ

Modifying tasks.json

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 đầu ra filename by replacing "$fileDirname$fileBasenameNoExtension.exe" with a hard-coded filename (for example "$workspaceFoldermyProgram.exe").


Debug helloworld.cpp

Next, you’ll create a launch.json tệp tin to configure VS Code to lớn launch the Microsoft C++ debugger when you press F5 to lớn debug the program. From the main thực đơn, choose Run > Add Configuration… và then choose C++ (Windows).

You’ll then see a dropdown for various predefined debugging configurations. Choose cl.exe build & debug active file.

*

VS Code creates a launch.json file, opens it in the editor, & builds & runs ‘helloworld’.

"version"

:

"0.2.0"

,

"configurations"

: <

"name"

:

"cl.exe build and debug active file"

,

"type"

:

"cppvsdbg"

,

"request"

:

"launch"

,

"program"

:

"$fileDirname

$fileBasenameNoExtension.exe"

,

"args"

: <>,

"stopAtEntry"

:

false

,

"cwd"

:

"$workspaceFolder"

,

"environment"

: <>,

"externalConsole"

:

false

,

"preLaunchTask"

:

"cl.exe build active file"

>

The program setting specifies the program you want khổng lồ debug. Here it is set to lớn the active file thư mục $fileDirname and active filename with the .exe extension $fileBasenameNoExtension.exe, which if helloworld.cpp is the active file will be helloworld.exe.

By default, the C++ extension won’t add any breakpoints to lớn your source code & the stopAtEntry value is set lớn false. Change the stopAtEntry value khổng lồ true to lớn cause the debugger khổng lồ stop on the main method when you start debugging.

Start a debugging session

Go back to lớn helloworld.cpp so that it is the active file.Press

F5

or from the main thực đối kháng choose Run > Start Debugging. Before you start stepping through the source code, let’s take a moment to notice several changes in the user interface:

The Integrated Terminal appears at the bottom of the source code editor. In the Debug Output tab, you see output đầu ra that indicates the debugger is up and running.

The editor highlights the first statement in the main method. This is a breakpoint that the C++ extension automatically sets for you:

*

The Run view on the left shows debugging information. You’ll see an example later in the tutorial.

At the đứng top of the code editor, a debugging control panel appears. You can move this around the screen by grabbing the dots on the left side.

Step through the code

Now you’re ready to lớn start stepping through the code.

Select the Step over icon in the debugging control panel until the for (const stringandamp; word : msg) statement is highlighted.

*

The Step Over command skip over all the internal function calls within the vector và string classes that are invoked when the msg variable is created and initialized. Notice the change in the Variables window on the left. In this case, the errors are expected because, although the variable names for the loop are now visible khổng lồ the debugger, the statement has not executed yet, so there is nothing lớn read at this point. The contents of msg are visible, however, because that statement has completed.

Press Step over again lớn advance khổng lồ the next statement in this program (skipping over all the internal code that is executed lớn initialize the loop). Now, the Variables window shows information about the loop variables.

Press Step over again to lớn execute the cout statement. Note As of the March 2019 version of the extension, no đầu ra is displayed until the loop completes.

If you like, you can keep pressing Step over until all the words in the vector have been printed to lớn the console. But if you are curious, try pressing the Step Into button to step through source code in the C++ standard library!

*

To return to your own code, one way is lớn keep pressing Step over. Another way is lớn set a breakpoint in your code by switching khổng lồ the helloworld.cpp tab in the code editor, putting the insertion point somewhere on the cout statement inside the loop, & pressing F9. A red dot appears in the gutter on the left to lớn indicate that a breakpoint has been mix on this line.

*

Then press F5 lớn start execution from the current line in the standard library header. Execution will break on cout. If you like, you can press F9 again to lớn toggle off the breakpoint.

Set a watch

Sometimes you might want lớn keep track of the value of a variable as your program executes. You can bởi vì this by setting a watch on the variable.

Place the insertion point inside the loop. In the Watch window, select the plus sign and in the text box, type word, which is the name of the loop variable. Now view the Watch window as you step through the loop.

*

Add another watch by adding this statement before the loop: int i = 0;. Then, inside the loop, showroom this statement: ++i;. Now add a watch for i as you did in the previous step.

To quickly view the value of any variable while execution is paused on a breakpoint, you can hover over it with the mouse pointer.

*

C/C++ configurations

If you want more control over the C/C++ extension, you can create a c_cpp_properties.json file, which will allow you to lớn change settings such as the path to the compiler, include paths, C++ standard (default is C++17), and more.

You can view the C/C++ configuration UI by running the command C/C++: Edit Configurations (UI) from the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)).

*

This opens the C/C++ Configurations page. When you make changes here, VS Code writes them lớn a file called c_cpp_properties.json in the .vscode folder.

*

Visual Studio Code places these settings in .vscodec_cpp_properties.json. If you open that file directly, it should look something like this:

"configurations"

: <

"name"

:

"Win32"

,

"includePath"

: <

"$workspaceFolder/**"

>,

"defines"

: <

"_DEBUG"

,

"UNICODE"

,

"_UNICODE"

>,

"windowsSdkVersion"

:

"10.0.18362.0"

,

"compilerPath"

:

"C:/Program Files (x86)/Microsoft Visual Studio/2019/BuildTools/VC/Tools/MSVC/14.24.28314/bin/Hostx64/x64/cl.exe"

,

"cStandard"

:

"c11"

,

"cppStandard"

:

"c++17"

,

"intelliSenseMode"

:

"msvc-x64"

>,

"version"

:

4

You only need to địa chỉ to the Include path array setting if your program includes header files that are not in your workspace or in the standard library path.

Compiler path

The compilerPath setting is an important setting in your configuration. The extension uses it to lớn infer the path to the C++ standard library header files. When the extension knows where to find those files, it can provide useful features like smart completions và Go to lớn Definition navigation.

The C/C++ extension attempts to lớn populate compilerPath with the default compiler location based on what it finds on your system. The extension looks in several common compiler locations.

The compilerPath tìm kiếm order is:

First test for the Microsoft Visual C++ compilerOpeThen look for g++ on Windows Subsystem for Linux (WSL)Then g++ for Mingw-w64.

If you have g++ or WSL installed, you might need to lớn change compilerPath to lớn match the preferred compiler for your project. For Microsoft C++, the path should look something lượt thích this, depending on which specific version you have installed: “C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64/cl.exe”.

Reusing your C++ configuration

VS Code is now configured to use the Microsoft C++ compiler. The configuration applies lớn the current workspace. Khổng lồ reuse the configuration, just sao chép the JSON files khổng lồ a .vscode folder in a new project folder (workspace) and change the names of the source file(s) và executable as needed.

Run VS Code outside the Developer Command Prompt

In certain circumstances, it isn’t possible to run VS Code from Developer Command Prompt for Visual Studio (for example, in Remote Development through SSH scenarios). In that case, you can automate initialization of Developer Command Prompt for Visual Studio during the build using the following tasks.json configuration:

"version"

:

"2.0.0"

,

"windows"

:

"options"

:

"shell"

:

"executable"

:

"cmd.exe"

,

"args"

: <

"/C"

,

// The path lớn VsDevCmd.bat depends on the version of Visual Studio you have installed.

"

"

C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/Tools/VsDevCmd.bat

"

"

,

"&&"

>

,

"tasks"

: <

"type"

:

"shell"

,

"label"

:

"cl.exe build active file"

,

"command"

:

"cl.exe"

,

"args"

: <

"/Zi"

,

"/EHsc"

,

"/Fe:"

,

"$fileDirname

$fileBasenameNoExtension.exe"

,

"$file"

>,

"problemMatcher"

: <

"$msCompile"

>,

"group"

:

"kind"

:

"build"

,

"isDefault"

:

true

>

Note: The path to VsDevCmd.bat might be different depending on the Visual Studio version or installation path. You can find the path to VsDevCmd.bat by opening a Command Prompt and running dir "VsDevCmd*" /s.

Troubleshooting

The term ‘cl.exe’ is not recognized

If you see the error “The term ‘cl.exe’ is not recognized as the name of a cmdlet, function, script file, or operable program.”, this usually means you are running VS Code outside of a Developer Command Prompt for Visual Studio & VS Code doesn’t know the path to lớn the cl.exe compiler.

You can always chạy thử that you are running VS Code in the context of the Developer Command Prompt by opening a new Terminal (⌃⇧` (Windows, Linux Ctrl+Shift+`)) and typing ‘cl’ khổng lồ verify cl.exe is available to lớn VS Code.

Next steps

Explore the VS Code User Guide.Review the Overview of the C++ extension.Create a new workspace, xào nấu your .vscode JSON files to it, adjust the necessary settings for the new workspace path, program name, and so on, và start coding!