How to Install (V142) Build Tools in Visual Studio

Visual Studio show me this error v142 tools

Moved from a comment into an answer:

This is a duplicate of this question. It seems the project was created on
a newer version of Visual Studio, that is 2019. You tagged the question with
visual-studio-2017, I suspect that is the problem.

- asynts Aug 24 at 12:01

Visual Studio 2017: build tools for v142 cannot be found error, even though Platform Toolset is set to v141

As @dxiv mentioned in the comments: "The error references one project, but the Property Pages refer to another." Every project in the solution (there should be two for OF projects, yourProjectName and openframeworksLib) needs to be individually downgraded. Instead of going to Project > Properties via the top toolbar, right click on each project in the Solution Explorer and get to the Properties menu for each of them from there.

screenshot

And I just realized the top toolbar's Project menu item coincides with whatever item you currently have selected from the Solution explorer.

How to build a visual studio 2019 project in vs 2022 without upgrading

If you take a look at the available visual studios components (this is the link for professional https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-professional?view=vs-2022&preserve-view=true ).

I believe the component id you are looking for is: Microsoft.VisualStudio.ComponentGroup.VC.Tools.142.x86.x64.

How to get MSVC MergeModules v142 in VisualStudio 2022?

This appears to be a bug in the Visual Studio 2022 installer: The merge modules component should be tied to which toolsets are installed, but it appears to install only the latest/current toolset's merge modules. The same is true for Visual Studio 2019; it appears that version is the only way to get the merge modules installed.

That said, merge modules are not recommended. The preferred method is to use the redistributable packages.

How to install multiple versions of MSBuild and use them with cmake

You only have 2022 installed, so you can't use any other generator. You installed toolkits using Visual Studio 2022. You can define the toolkit using the command line, e.g.:

cmake .. -G "Visual Studio 17 2022" -T v142

See https://cmake.org/cmake/help/latest/manual/cmake.1.html.



Related Topics



Leave a reply



Submit