7

As written here, under "Project Settings" I should be able to specify the compiler to be used for the current project. However, I cannot find this menu entry in Visual Studio 2019.

I have both Visual C++ 2019 and 2013, and would like to use the new IDE with the old compiler. How can I do it?

Is it possible to do it with the "Community" editions?

Das_Geek
  • 2,775
  • 7
  • 20
  • 26
Pietro
  • 12,086
  • 26
  • 100
  • 193

1 Answers1

8

Here are the official instructions, taken from this page:

  1. In Visual Studio, in Solution Explorer, open the shortcut menu for your project (not for your solution) and then choose Properties to open your project Property Pages dialog box.

  2. In the Property Pages dialog box, open the Configuration drop-down list and then select All Configurations.

  3. In the left pane of the dialog box, expand Configuration Properties and then select General.

  4. In the right pane, select Platform Toolset and then select the toolset you want from the drop-down list. For example, if you have installed the Visual Studio 2010 toolset, select Visual Studio 2010 (v100) to use it for your project.

  5. Choose the OK button.

You can see a screenshot of my window below:

screenshot of config window

Das_Geek
  • 2,775
  • 7
  • 20
  • 26
  • The only option I can see related to the compiler is the "C++ Language Standard", which can be set to C++14, C++17 and C++Latest. I cannot see anything about the possibility to specify a different compiler. – Pietro Apr 29 '19 at 14:34
  • @Pietro When you go into your Visual Studio Installer, select Modify, and go to the Individual Components tab, do you see anything other than the latest MSVC option selected in the Compiler section? – Das_Geek Apr 29 '19 at 14:45
  • The MSVC versions I ticked are "MSCV v140 - VS 2015 C++ build tools (v14.00)" and "MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.20)". So I should have at least two compilers to choose from... – Pietro Apr 29 '19 at 15:45
  • 1
    @Pietro See my edits to get the updated solution. Looks like the original pages I linked were updated recently, but did not apply to the most recent version of VS. – Das_Geek Apr 29 '19 at 16:51