[mpir] build failure about vcpkg HOT 7 OPEN

Does this also apply to you: SpecFlowOSS/SpecFlow#1250 (comment) ?

from vcpkg.

As noted the newer MSBuild (from VS2017) does work, but the goal is to run that with a VS2015 stack (which worked before).

from vcpkg.

Was probably changed in #33142

from vcpkg.

@Neumann-A Can you please verify if this failure is related to your changes (and possibly how to work around that without reversing the commit)?

from vcpkg.

You should really be using VS 2022 with the v140 toolset instead of expecting that a 2023 change will work with VS2015.
There is probably a workaround by using an overlay for vcpkg-msbuild removing the problematic field but I am not going to investigate that possibility.

from vcpkg.

vcpkg says that VC2015 is expected to work.

It is not that I'd like to keep that forever, but I do know some people/companies still use VC2015 and have VC2015 generated DLLs that need to work toghether, so "just using a newer toolset" is likely not what will work there.

Is it possible to request to use an older definition? Maybe by updating the ports definitions, then manually downgrading the mpir definition to the last version that worked before installing?

from vcpkg.

V140 is the old toolset which can be installed via the installer. Just use a newer MSBuild/Visual Studio

If you use manifest mode you can pin whatever version you like.

from vcpkg.