Using GCC with MinGW

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

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

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

    1. Install .

    2. Install the C/C++ extension for VS Code. You can install the C/C++ extension by searching for ‘c++’ in the Extensions view ().

    3. You will install Mingw-w64 via the SourceForge website. Click Mingw-w64 to begin downloading the compressed archive file. Extract the tools from the compressed file to a folder that has no spaces in its path. In this tutorial, we assume it is installed under C:\mingw-w64.

    4. Add the path to your Mingw-w64 bin folder to the Windows PATH environment variable.

      1. In the Windows search bar, type ‘settings’ to open your Windows Settings.
      2. Search for Edit environment variables for your account.
      3. Choose the Path variable and then select Edit.
      4. Select New and add the Mingw-w64 path to the system path. The exact path depends on which version of Mingw-w64 you have installed and where you installed it. Here is an example: c:\mingw-w64\x86_64-8.1.0-win32-seh-rt_v6-rev0\mingw64\bin.
      5. Select OK to save the Path update. You will need to reopen any console windows for the new PATH location to be available.

    To check that your Mingw-w64 tools are correctly installed and available, open a new Command Prompt and type:

    If you don’t see the expected output or g++ or gdb is not a recognized command, check your installation (Windows Control Panel > Programs) and make sure your PATH entry matches the Mingw-w64 location.

    Create Hello World

    From a Windows command prompt, create an empty folder called projects where you can place all your VS Code projects. Then create a sub-folder called helloworld, navigate into it, and open VS Code in that folder by entering the following commands:

    1. mkdir projects
    2. cd projects
    3. mkdir helloworld
    4. cd helloworld
    5. 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 folder 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 File Explorer title bar, select the New File button and name the file helloworld.cpp.

    Now paste in this source code:

    Now press kb(workbench.action.files.save) to save the file. Notice how the file you just added appears in the File Explorer view (kb(workbench.view.explorer)) in the side bar of VS Code:

    You can also enable to automatically save your file changes, by checking Auto Save in the main File menu.

    The Activity Bar on the far left lets you open different views such as Search, Source Control, and 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.

    Explore IntelliSense

    In your new helloworld.cpp file, hover over vector or string to see type information. After the declaration of the msg variable, start typing msg. as you would when calling a member function. You should immediately see a completion list that shows all the member functions, and a window that shows the type information for the msg object:

    Statement completion IntelliSense

    You can press the kbstyle(Tab) key to insert the selected member; then, when you add the opening parenthesis, you will see information about any arguments that the function requires.

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

    From the main menu, choose Terminal > Configure Default Build Task. In the dropdown, which will display a tasks dropdown listing various predefined build tasks for C++ compilers. Choose g++.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 folder and open it in the editor.

    1. "version": "2.0.0",
    2. "tasks": [
    3.     {
    4.         "type": "shell",
    5.         "label": "g++.exe build active file",
    6.         "command": "C:\\mingw-w64\\i686-8.1.0-posix-dwarf-rt_v6-rev0\\mingw32\\bin\\g++.exe",
    7.         "args": [
    8.             "-g",
    9.             "${file}",
    10.             "-o",
    11.             "${fileDirname}\\${fileBasenameNoExtension}.exe"
    12.         ],
    13.         "options": {
    14.             "cwd": "C:\\mingw-w64\\i686-8.1.0-posix-dwarf-rt_v6-rev0\\mingw32\\bin"
    15.         },
    16.         "problemMatcher": [
    18.         ],
    19.         "group": {
    20.             "kind": "build",
    21.             "isDefault": true
    22.         }
    23.     }
    24. ]
    25. }

    The command setting specifies the program to run; in this case that is g++. The args array specifies the command-line arguments that will be passed to g++. These arguments must be specified in the order expected by the compiler. This task tells g++ to take the active file (${file}), compile it, and create an executable file 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.

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

    The "isDefault": true value in the group object specifies that this task will be run when you press kb(workbench.action.tasks.build). This property is for convenience only; if you set it to false, you can still run it from the Terminal menu with Tasks: Run Build Task.

    Running the build

    1. Go back to helloworld.cpp. Your task builds the active file and you want to build helloworld.cpp.

    2. To run the build task defined in tasks.json, press kb(workbench.action.tasks.build) or from the Terminal main menu choose Tasks: Run Build Task.

    3. 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 g++ build, the output looks something like this:

    4. Create a new terminal using the + button and you’ll have a new terminal (running PowerShell) with the helloworld folder as the working directory. Run dir and you should now see the executable helloworld.exe.

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

    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").

    Debug helloworld.cpp

    Next, you’ll create a launch.json file to configure VS Code to launch the GDB debugger when you press kb(workbench.action.debug.start) to debug the program. From the main menu, choose Run > Add Configuration… and then choose C++ (GDB/LLDB).

    You’ll then see a dropdown for various predefined debugging configurations. Choose g++.exe build and debug active file.

    C++ debug configuration dropdown

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

    The program setting specifies the program you want to debug. Here it is set to the active file folder ${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 your source code and the stopAtEntry value is set to false. Change the stopAtEntry value to true to cause the debugger to stop on the main method when you start debugging.

    Start a debugging session

    1. Go back to helloworld.cpp so that it is the active file.
    2. Press kb(workbench.action.debug.start) or from the main menu 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 that indicates the debugger is up and running.

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

    • At the 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 start stepping through the code.

    1. Click or press the Step over icon in the debugging control panel.

      This will advance program execution to the first line of the for loop, and skip over all the internal function calls within the vector and 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 to the debugger, the statement has not executed yet, so there is nothing to read at this point. The contents of msg are visible, however, because that statement has completed.

    2. Press Step over again to advance to the next statement in this program (skipping over all the internal code that is executed to initialize the loop). Now, the Variables window shows information about the loop variables.

    3. Press Step over again to execute the cout statement. (Note that as of the March 2019 release, the C++ extension does not print any output to the Debug Console until the loop exits.)

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

      Breakpoint in gcc standard library header

      To return to your own code, one way is to keep pressing Step over. Another way is to set a breakpoint in your code by switching to the helloworld.cpp tab in the code editor, putting the insertion point somewhere on the cout statement inside the loop, and pressing kb(editor.debug.action.toggleBreakpoint). A red dot appears in the gutter on the left to indicate that a breakpoint has been set on this line.

      Then press kb(workbench.action.debug.start) to start execution from the current line in the standard library header. Execution will break on cout. If you like, you can press kb(editor.debug.action.toggleBreakpoint) again to toggle off the breakpoint.

      When the loop has completed, you can see the output in the Integrated Terminal, along with some other diagnostic information that is output by GDB.

      Debug output in terminal

    Sometimes you might want to keep track of the value of a variable as your program executes. You can do this by setting a watch on the variable.

    1. Place the insertion point inside the loop. In the Watch window, click 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.

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

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

      Mouse hover

    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 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 (kb(workbench.action.showCommands)).

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

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

    1. {
    2. "configurations": [
    3.     {
    4.         "name": "Win32",
    5.         "includePath": [
    6.             "${workspaceFolder}/**"
    7.         ],
    8.         "defines": [
    9.             "_DEBUG",
    10.             "UNICODE",
    11.             "_UNICODE"
    12.         ],
    13.         "compilerPath": "C:\\mingw-w64\\i686-8.1.0-posix-dwarf-rt_v6-rev0\\mingw32\\bin\\gcc.exe",
    14.         "cStandard": "c11",
    15.         "cppStandard": "c++17",
    16.         "intelliSenseMode": "clang-x86"
    17.     }
    18. ],
    19. "version": 4
    20. }

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

    The compilerPath setting is an important setting in your configuration. The extension uses it to 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 and Go to Definition navigation.

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

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

    If you have Visual Studio or WSL installed, you may need to change compilerPath to match the preferred compiler for your project. For example, if you installed Mingw-w64 version 8.1.0 under C:\mingw-w64, using the Win32 threads and SEH exception handling options, the path would look like this: C:\mingw-w64\x86_64-8.1.0-win32-seh-rt_v6-rev0\mingw64\bin\g++.exe.

    Next steps

    • Explore the .
    • Create a new workspace, copy your JSON files to it, adjust the necessary settings for the new workspace path, program name, and so on, and start coding!