This issue is first reported on Developer Community.
After enable Use Vcpkg Manifest and adding a vcpkg.json file into a c++ project in Visual Studio, the following steps will be added into the build steps:
Target VcpkgTripletSelection
Target VcpkgInstallManifestDependencies
The Target VcpkgInstallManifestDependencies step often takes more than 3 seconds to detect package changes when building, regardless of any changes to the project.
For example, just add a space in the cpp file, under normal circumstances the build step will be finished immediately, but now the VcpkgInstallManifestDependencies step will be executed first, and after a few seconds, the compilation and linking steps will be finished immediately.
Customer hopes that the VcpkgInstallManifestDependencies step will be executed only after there are vcpkg-related modifications, and it will be skipped when building general source modifications.
This issue is first reported on Developer Community.
After enable Use Vcpkg Manifest and adding a vcpkg.json file into a c++ project in Visual Studio, the following steps will be added into the build steps:
Target VcpkgTripletSelection
Target VcpkgInstallManifestDependencies
The Target VcpkgInstallManifestDependencies step often takes more than 3 seconds to detect package changes when building, regardless of any changes to the project.
For example, just add a space in the cpp file, under normal circumstances the build step will be finished immediately, but now the VcpkgInstallManifestDependencies step will be executed first, and after a few seconds, the compilation and linking steps will be finished immediately.
Customer hopes that the VcpkgInstallManifestDependencies step will be executed only after there are vcpkg-related modifications, and it will be skipped when building general source modifications.