You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was a bit of a nightmare to figure out. For a reason I can't explain msquic fails to build if vcpkg is cloned into a path with more than 64 chars. Steps to reproduce:
cd C:/
mkdir 01234567890123456789012345678901234567890123456789012345678901
cd 01234567890123456789012345678901234567890123456789012345678901
git clone https://github.com/microsoft/vcpkg vcpkg
cd vcpkg
./bootstrap-vcpkg.bat
vcpkg.exe install msquic
If you clone vcpkg into dir which path, including drive letter, is 64 chars or less then it builds just fine.
The text was updated successfully, but these errors were encountered:
redbaron
changed the title
[msquic] Build error on arm64-windows if vcpkg dir parent path more than 63 chars
[msquic] Build error on arm64-windows if vcpkg dir parent path more than 64 chars
Oct 30, 2024
@redbaron, thanks for posting this question, you can use the parameter --x-buildtrees-root= to specify the path to install, such as: ./vcpkg.exe install msquic --x-buildtrees-root=F:\test\012\vcpkg
It is a build failure report, certainly not a question. I spend 2 hours reducing unexplainable build failure to this minimal case and I can't be the only one.
if it is a known limitation, vcpkg could do A LOT more:
vcpkg should read builtree path from env var and setup instructions should encourage users to use it. It will help users who pull vcpkg as a submodule, not a standalone ENV{VCPKG_ROOT} clone
if it detects long path on build error it could hint a user that it might be due to it
there seems to be avcpkg_buildpath_length_warning helper. Each individual port has to self-report as potentially problematic, even though my understanding that ALL of them can fail build given long enough vcpkg clone location. Now that msquic is known to be susceptible to it this build failure report definitely has something to do with port: it should make use of vcpkg_buildpath_length_warning at the very least.
This was a bit of a nightmare to figure out. For a reason I can't explain
msquic
fails to build if vcpkg is cloned into a path with more than 64 chars. Steps to reproduce:If you clone vcpkg into dir which path, including drive letter, is 64 chars or less then it builds just fine.
Package: msquic:[email protected]#1
Host Environment
vcpkg-scripts version: bb1ca27 2024-10-29 (20 hours ago)
To Reproduce
vcpkg install msquic
Failure logs
C:\01234567890123456789012345678901234567890123456789012345678901\vcpkg\buildtrees\msquic\install-arm64-windows-dbg-out.log
The text was updated successfully, but these errors were encountered: