Host Environment

• OS: Windows
• Compiler: VS2022

To Reproduce

Steps to reproduce the behavior:

./vcpkg install qt:x64-windows

Failure logs
Installing 38/41 qtwebengine:x64-windows...
Building qtwebengine[core,default-features,geolocation,spellchecker,webchannel]:x64-windows...
-- Setting up python virtual environmnent...
-- Installing python packages: html5lib
-- Setting up python virtual environmnent...finished.
CMake Warning at ports/qtwebengine/portfile.cmake:85 (message):
Buildtree path 'C:/dev/vcpkg/buildtrees/qtwebengine' is too long.

Consider passing --x-buildtrees-root=<shortpath> to vcpkg!

Trying to use 'C:/dev/vcpkg/buildtrees/qtwebengine/../tmp'
Call Stack (most recent call first):
scripts/ports.cmake:147 (include)

CMake Error at ports/qtwebengine/portfile.cmake:90 (message):
Buildtree path is too long. Build will fail! Pass
--x-buildtrees-root=<shortpath> to vcpkg
Call Stack (most recent call first):
scripts/ports.cmake:147 (include)

error: building qtwebengine:x64-windows failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with 'git pull' and 'vcpkg update'.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+qtwebengine
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[qtwebengine]+Build+error
Include '[qtwebengine] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2022-11-10-5fdee72bc1fceca198fb1ab7589837206a8b81ba
vcpkg-scripts version: 30a20e8f1 2022-12-07 (11 days ago).
- Attach ***every failure log file*** mentioned in the console output.

The console output by itself is not enough to investigate a build failure.
Some hint to where the log files are located would help... VCPKG creates a LOT of files!

Additional context

The command was run from the 'x64 Native Tools Command Prompt for VS 2022'. It failed on two (2) separate machines. git pull and vcpkg update had been run previously with zero changes, as it is a brand shiny new install on new laptops.

stdout-x64-windows.log
pip-install-virtualenv-x64-windows-out.log
pip-install-packages-x64-windows-out.log