Installing a C++ Compiler on Your Own PC

Steven J. Zeil

This document will walk you through the process of installing a free C++ compiler on your PC.

Do you need to do this?

I assume that you are here because you want the ability to do at least some of your programming work on your own PC. You do have the option, though, of connecting remotely to CS Dept machines and doing all your work there.

• CS252 is devoted to teaching you how to do this with the Dept’s Linux servers.
• You can also work remotely in a Windows environment via the CS Dept’s Virtual Lab.

So, no, ODU CS students don’t **need* to do this. But many will find it convenient to put together a programming environment on their own PCs.

What will you need to get?

By the end of this process, you need to have installed

• the compiler itself, g++ or clang
• the gdb debugger
• the make build manager

What will this let you do?

It will let you compile, run, and debug C++ code when working from the command line.

Of course, most people don’t want to do all of their work from the command line. Furthermore, conspicuously missing from this list is any means of creating or editing code.

That’s because a compiler is a very specific thing – a program that translates your programming language source code into an executable. A compiler is not a program that allows you to create, edit, run, test, & debug your code. Code::Blocks , Eclipse , XCode , etc. are not compilers – they are IDEs.

You’ll want an IDE

An IDE (Integrated Development Environment) is a program that “surrounds” a compiler and provides support for a variety of programming activities, including writing code, compiling it, correcting errors, running and testing the resulting program, and debugging the program.

The most popular IDEs for C++ programming at ODU are Code::Blocks and Eclipse. Both IDEs are free, and both can be installed on Windows, OS/X, and Linux PCs.

In most cases, though, you want to install your compiler and make sure it’s working before you install your IDE.

Decision Time

1 Installing a C++ Compiler in Linux

If you are running Linux on your PC, you presumably already know how to install new software packages in your Linux distribution. This is just another package.

Follow the usual procedure for installing packages on your system and get the latest versions of

2 Installing a C++ Compiler on Apple OS/X

g++ is no longer available as an official Apple distribution. However, you can obtain the clang C++ compiler, a worthy “competitor” to g++ that has a very loyal following, in a package called “Command Line Tools for XCode” available from Apple’s developer Site.

That should also install gdb and make as well.

3 Installing a C++ Compiler on Microsoft Windows

You have two main options here, CygWin and MingW .

The CygWin package provides a Posix layer in Windows, allowing much Unix software to be compiled and run without modification. When you install CygWin, you get a good command shell ( bash ), which may be useful in its own right. The g++ compiler can also be selected from the CygWin setup utility.

A disadvantage of CygWin is that the compiler produces code that relies on the Posix layer, which in turn is provided by a CygWin DLL. Binary executables produced by the CygWin port of g++ can only be run on other machines that have a copy of that DLL.

MinGW, a “spin-off” project from CygWin, provides an alternate port of the g++ compiler that works without a special DLL. You may have used this already, as this is the g++ typically shipped with Code::Blocks and other basic Windows IDEs.

Both the Code::Blocks and Eclipse IDEs will work with either CygWin or MinGW.

If you have decided that you are going to install Code::Blocks as your IDE, you have the option of stopping right now and moving directly to installing that IDE. That’s because Code::Blocks for Windows is distributed in two flavors: one with no compiler of its own, and the other pre-packaged with a version of the MinGW compiler.

3.1 Installing the CygWin Compiler

If you prefer the MingW version, jump to the next section.

Go to the CygWin site and follow the directions to download and then run the CygWin installer program.

I recommend just installing the basic, default CygWin system on your first “pass” without adding any optional packages (including the compiler).

Check your installation to make sure it works. You should have a new Start menu entry to run a CygWin terminal . Try it and make sure that it works. It should run a bash command shell that accepts commands like:

• pwd : to print your current working directory location
• ls : to list the files and directories in your current working directory
• cd directory : to change your current working directory location
• exit : to close the terminal session.

If everything looks good, re-run the CygWin setup program and add the following: g++ , gdb , and make .

Check your installation to make sure it works. Start a CygWin terminal again. Give the commands

Each should result in a message indicating that the program started successfully.

3.2 Installing the MinGW Compiler

Go the the MinGW site and follow the directions to download and then run the MinGW installer program.

Install the following: mingw-developer-toolkit, mingw32-gcc-g++, mingw32-gdb, msys-base, msys-make

Check your installation. Open a Windows cmd window. (Click the Windows start button and type “cmd”). Step down to the bin directory inside the directory where you installed MinGW, for example, if you installed it in the default location of C:\MinGW , then you should do

Give the commands

Each should result in a message indicating that the program started successfully.

3.3 Add the Compilers to your PATH

The %PATH% in Windows is the list of directories where Windows will search for executable programs.

Whichever compiler you choose, add the bin directory containing the g++ and other compiler executables to your Windows PATH. Whatever IDE you install later, this step will help the IDE find your compiler (especially if you did not install them in the default location.)

Check that you have done so successfully: Open a Windows cmd window. (Click the Windows start button and type “cmd”).

Enter the following commands:

(If you installed MinGW, change the make command above to mingw32-make .) Each should result in a message indicating that the program was located and started successfully.

4 What Now?

Next it’s time to install an IDE.

1: : Actually, even that decision can be worked around. Some students use VirtualBox or similar packages to run Linux virtual machines on their Windows/Mac PCs. Windows 10 users also now have the option of running Ubuntu Linux within a “sandbox” on Windows.

Walkthrough: Compiling a Native C++ Program on the Command Line

Visual Studio includes a command-line C and C++ compiler. You can use it to create everything from basic console apps to Universal Windows Platform apps, Desktop apps, device drivers, and .NET components.

In this walkthrough, you create a basic, «Hello, World»-style C++ program by using a text editor, and then compile it on the command line. If you’d like to try the Visual Studio IDE instead of using the command line, see Walkthrough: Working with Projects and Solutions (C++) or Using the Visual Studio IDE for C++ Desktop Development.

In this walkthrough, you can use your own C++ program instead of typing the one that’s shown. Or, you can use a C++ code sample from another help article.

Prerequisites

To complete this walkthrough, you must have installed either Visual Studio and the optional Desktop development with C++ workload, or the command-line Build Tools for Visual Studio.

Visual Studio is an integrated development environment (IDE). It supports a full-featured editor, resource managers, debuggers, and compilers for many languages and platforms. Versions available include the free Visual Studio Community edition, and all can support C and C++ development. For information on how to download and install Visual Studio, see Install C++ support in Visual Studio.

The Build Tools for Visual Studio installs only the command-line compilers, tools, and libraries you need to build C and C++ programs. It’s perfect for build labs or classroom exercises and installs relatively quickly. To install only the command-line tools, look for Build Tools for Visual Studio on the Visual Studio Downloads page.

Before you can build a C or C++ program on the command line, verify that the tools are installed, and you can access them from the command line. Visual C++ has complex requirements for the command-line environment to find the tools, headers, and libraries it uses. You can’t use Visual C++ in a plain command prompt window without doing some preparation. Fortunately, Visual C++ installs shortcuts for you to launch a developer command prompt that has the environment set up for command line builds. Unfortunately, the names of the developer command prompt shortcuts and where they’re located are different in almost every version of Visual C++ and on different versions of Windows. Your first walkthrough task is finding the right one to use.

A developer command prompt shortcut automatically sets the correct paths for the compiler and tools, and for any required headers and libraries. You must set these environment values yourself if you use a regular Command Prompt window. For more information, see Set the Path and Environment Variables for Command-Line Builds. We recommend you use a developer command prompt shortcut instead of building your own.

Open a developer command prompt

If you have installed Visual Studio 2017 or later on Windows 10, open the Start menu and choose All apps. Scroll down and open the Visual Studio folder (not the Visual Studio application). Choose Developer Command Prompt for VS to open the command prompt window.

If you have installed Microsoft Visual C++ Build Tools 2015 on Windows 10, open the Start menu and choose All apps. Scroll down and open the Visual C++ Build Tools folder. Choose Visual C++ 2015 x86 Native Tools Command Prompt to open the command prompt window.

You can also use the Windows search function to search for «developer command prompt» and choose one that matches your installed version of Visual Studio. Use the shortcut to open the command prompt window.

Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter cl and verify that the output looks something like this:

There may be differences in the current directory or version numbers. These values depend on the version of Visual C++ and any updates installed. If the above output is similar to what you see, then you’re ready to build C or C++ programs at the command line.

If you get an error such as «‘cl’ is not recognized as an internal or external command, operable program or batch file,» error C1034, or error LNK1104 when you run the cl command, then either you are not using a developer command prompt, or something is wrong with your installation of Visual C++. You must fix this issue before you can continue.

If you can’t find the developer command prompt shortcut, or if you get an error message when you enter cl , then your Visual C++ installation may have a problem. Try reinstalling the Visual C++ component in Visual Studio, or reinstall the Microsoft Visual C++ Build Tools. Don’t go on to the next section until the cl command works. For more information about installing and troubleshooting Visual C++, see Install Visual Studio.

Depending on the version of Windows on the computer and the system security configuration, you might have to right-click to open the shortcut menu for the developer command prompt shortcut and then choose Run as administrator to successfully build and run the program that you create by following this walkthrough.

Create a Visual C++ source file and compile it on the command line

In the developer command prompt window, enter md c:\hello to create a directory, and then enter cd c:\hello to change to that directory. This directory is where both your source file and the compiled program get created.

Enter notepad hello.cpp in the command prompt window.

Choose Yes when Notepad prompts you to create a new file. This step opens a blank Notepad window, ready for you to enter your code in a file named hello.cpp.

In Notepad, enter the following lines of code:

This code is a simple program that will write one line of text on the screen and then exit. To minimize errors, copy this code and paste it into Notepad.

Save your work! In Notepad, on the File menu, choose Save.

Congratulations, you’ve created a C++ source file, hello.cpp, that is ready to compile.

Switch back to the developer command prompt window. Enter dir at the command prompt to list the contents of the c:\hello directory. You should see the source file hello.cpp in the directory listing, which looks something like:

The dates and other details will differ on your computer.

If you don’t see your source code file, hello.cpp , make sure the current working directory in your command prompt is the C:\hello directory you created. Also make sure that this is the directory where you saved your source file. And make sure that you saved the source code with a .cpp file name extension, not a .txt extension. Your source file gets saved in the current directory as a .cpp file automatically if you open Notepad at the command prompt by using the notepad hello.cpp command. Notepad’s behavior is different if you open it another way: By default, Notepad appends a .txt extension to new files when you save them. It also defaults to saving files in your Documents directory. To save your file with a .cpp extension in Notepad, choose File > Save As. In the Save As dialog, navigate to your C:\hello folder in the directory tree view control. Then use the Save as type dropdown control to select All Files (*.*). Enter hello.cpp in the File name edit control, and then choose Save to save the file.

At the developer command prompt, enter cl /EHsc hello.cpp to compile your program.

The cl.exe compiler generates an .obj file that contains the compiled code, and then runs the linker to create an executable program named hello.exe. This name appears in the lines of output information that the compiler displays. The output of the compiler should look something like:

If you get an error such as «‘cl’ is not recognized as an internal or external command, operable program or batch file,» error C1034, or error LNK1104, your developer command prompt is not set up correctly. For information on how to fix this issue, go back to the Open a developer command prompt section.

If you get a different compiler or linker error or warning, review your source code to correct any errors, then save it and run the compiler again. For information about specific errors, use the search box to look for the error number.

To run the hello.exe program, at the command prompt, enter hello .

The program displays this text and exits:

Congratulations, you’ve compiled and run a C++ program by using the command-line tools.

Next steps

This «Hello, World» example is about as simple as a C++ program can get. Real world programs usually have header files, more source files, and link to libraries.

You can use the steps in this walkthrough to build your own C++ code instead of typing the sample code shown. These steps also let you build many C++ code sample programs that you find elsewhere. You can put your source code and build your apps in any writeable directory. By default, the Visual Studio IDE creates projects in your user folder, in a source\repos subfolder. Older versions may put projects in a *Documents\Visual Studio \Projects folder.

To compile a program that has additional source code files, enter them all on the command line, like:

cl /EHsc file1.cpp file2.cpp file3.cpp

The /EHsc command-line option instructs the compiler to enable standard C++ exception handling behavior. Without it, thrown exceptions can result in undestroyed objects and resource leaks. For more information, see /EH (Exception Handling Model).

When you supply additional source files, the compiler uses the first input file to create the program name. In this case, it outputs a program called file1.exe. To change the name to program1.exe, add an /out linker option:

cl /EHsc file1.cpp file2.cpp file3.cpp /link /out:program1.exe

And to catch more programming mistakes automatically, we recommend you compile by using either the /W3 or /W4 warning level option:

cl /W4 /EHsc file1.cpp file2.cpp file3.cpp /link /out:program1.exe

The compiler, cl.exe, has many more options. You can apply them to build, optimize, debug, and analyze your code. For a quick list, enter cl /? at the developer command prompt. You can also compile and link separately and apply linker options in more complex build scenarios. For more information on compiler and linker options and usage, see C/C++ Building Reference.

You can use NMAKE and makefiles, MSBuild and project files, or CMake, to configure and build more complex projects on the command line. For more information on using these tools, see NMAKE Reference, MSBuild, and CMake projects in Visual Studio.

The C and C++ languages are similar, but not the same. The MSVC compiler uses a simple rule to determine which language to use when it compiles your code. By default, the MSVC compiler treats files that end in .c as C source code, and files that end in .cpp as C++ source code. To force the compiler to treat all files as C++ independent of file name extension, use the /TP compiler option.

The MSVC compiler includes a C Runtime Library (CRT) that conforms to the ISO C99 standard, with minor exceptions. Portable code generally compiles and runs as expected. Certain obsolete library functions, and several POSIX function names, are deprecated by the MSVC compiler. The functions are supported, but the preferred names have changed. For more information, see Security Features in the CRT and Compiler Warning (level 3) C4996.