[New Environment variable] add an Environment variable like VCPKG_DISABLE to disable vcpkg integration once but not global

[congzhangzh]

Is your feature request related to a problem? Please describe.

node windows compile failed if zlib is installed by vcpkg and vcpkg integration install is done

I can confirm that because the node link error gone after vcpkg integration remove

Ref: nodejs/node#24448

Proposed solution

add VCPKG_DISABLE to disable vcpkg integration for the child process, because my other c++ project depend on vcpkg integration.

this can be done either skip on user side, or system side:

Describe alternatives you've considered

do vcpkg integration remove and run other c++ project with cmake toolchain

Additional context

https://learn.microsoft.com/en-us/vcpkg/users/config-environment

[FrankXie05]

@congzhangzh Thanks for posting this issue.
For each project, their property interface has a corresponding button Use Vcpkg to enable vcpkg.
If you only want some sub-projects to use vcpkg, you only need to open the corresponding property interface and set Use Vcpkg to No.

[congzhangzh]

@FrankXie05 tks for your replay, that's a way, but that's not always possible, especially for batch shell script.

for example, if I can pass something to msbuild I can do

msbuild ... /p:UseVcpkg=false

I already do this: https://github.com/congzhangzh/node/blob/66a6e5ee463491b6c0416d4393cd27bf985747a5/vcbuild.bat#L335

but if this happened for some inner call, for example, A shell call B, B shell call C, and C need to disable vcpkg, and A=>B can not accept and pass something to C's msbuild, like B&C is some third party application or shell, I can do nothing.

[congzhangzh]

something like Directory.build.props is another way, but that's another story:)