ConsoleZ.sln uses v142 toolset but is in VS2017 format?

[chrisant996]

What configuration should I be using to compile Console?

I'm trying to compile Console because I want to track down and offer a fix for what may be a bug in ANSI escape code handling in a particular case. (I see in the wiki that Console doesn't process ANSI escape codes. The issue occurs only in Console, not in conhost or ConEmu or Windows Terminal. I want to examine Console in the debugger to be able to identify how/whether it's somehow involved. Regardless, I want to be able to build it to test changes since the April 2019 release, and to be able to potentially contribute in the future.)

When I start ConsoleZ.sln, it gets auto-detected as a VS2017 solution and loads in VS2017. But when trying to build in VS2017 it reports errors because the vcxproj files target the v142 toolset, which is part of VS2019. Looking at source logs for the vcxproj files, they were explicitly changed to reference "v142" toolset and the commit description mentions Visual Studio 2019. VS2019 refuses to open the ConsoleZ.sln file without converting it to VS2019, so it seems that I'm having trouble replicating the intended build environment.

Background:

• I'm the current maintainer of Clink and am well versed in C++ and Visual Studio in general.
• I have both VS2017 Enterprise and VS2019 Enterprise installed side by side, and keep them fully updated.

[chrisant996]

Oh, and the latest experimental build does not reproduce the ANSI escape code problem, so that appears to have been addressed.

However, I would still like to be able to build Console using the same development environment as the repo expects. (I can of course make local changes, but then I won't be able to verify whether pull requests from me will build correctly for others.)

[keminar]

Error MSB8020 Cannot find the build tools for v142 (Platform Toolset = “v142”). To build using the v142 build tools, please install the v142 build tools.

1. Open the project's property page. Right-click the project in the Solution Explorer and select "Properties".

2. In "Configuration Properties" -> "General", find the "Platform Toolset" option.

3. Select "Visual Studio 2017 - Windows XP (v141_xp)" or "Visual Studio 2017 (v141)" from the drop-down list.

Error C1083 Cannot open include file: “boost/format.hpp”: No such file or directory

The Boost library is not installed: Since the Boost library is not installed in the system, the corresponding header file cannot be found naturally.

You can download the Boost library version suitable for Windows from the official Boost website, and then install it according to the official documentation. The installation steps for common operating systems are given below:

Extract the downloaded Boost compressed package.

1. Open the Command Prompt and switch to the extracted Boost directory.

2. Run the bootstrap.bat script to generate the b2.exe build tool.

3. Run the b2 install command for installation.

Configure the compiler include path

After installing the Boost library, you need to configure the compiler's include path in Visual Studio so that the compiler can find the header files of the Boost library. The specific steps are as follows:

1. Open Visual Studio, right-click the project in the Solution Explorer, and select "Properties".

2. In "Configuration Properties" -> "C/C++" -> "General", find the "Additional Include Directories" option.

3. Click the drop-down arrow on the right side of "Additional Include Directories" and select "Edit".

4. In the pop-up dialog box, click the "New" button, and then add the directory where the Boost library header files are located. For example, if the Boost library is installed in the C:\boost_1_78_0 directory, you need to add C:\boost_1_78_0 to the include directories.

5. Click "OK" to save the settings.

Error RC1015 cannot open include file 'afxres.h'.

The MFC library is not installed: Since the MFC library is not installed in the system, the resource compiler cannot find the afxres.h file.

You can confirm whether the MFC library is installed through the Visual Studio Installer. The steps are as follows:

1. Open the Visual Studio Installer.

2. In the "Installed" tab, find the version of Visual Studio you installed and click "Modify".

3. In the "Workloads" tab, make sure that "Desktop development with C++" is checked.

4. Expand the "Desktop development with C++" workload and confirm that "C++ MFC for x86 and x64" is checked.

5. If it is not checked, check this option, and then click the "Modify" button for installation.