Build seems to be susceptible to long-path problems

[mschofie]

I initially cloned the repo into (for example):

Q:\Source\github\microsoft\Attestation-Client-Samples

And with that path, I get build failures that appear to be related to hitting 'long path' problems. Infact, cloning into:

Q:\Attestation-Client-Samples

I also hit problems. It wasn't until I ran "subst m: Q:\Source\github\microsoft\Attestation-Client-Samples" and built from "m:" (using CMake) that I could successfully build. Unfortunately, if I try and open the "m:" folder in Visual Studio (17.12), it doesn't open the solution - that appears to be a bug in Visual Studio.

[mschofie]

Just to clarify, it's the VCPkg dependencies that fail, causing the whole build to fail. Once the VCPkg builds have built, they're in a cache, and then work anywhere. So if you build from a "short" clone path, and then build from a longer clone path, then things will work. To repro, you'd have to delete your VCPkg cache - which is in $env:LOCALAPPDATA\vcpkg for me.