We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
I tried running the buildscript and it overwrote C:\B\ with QT as part of the process.
This was already in use for something else. Luckily I keep backups.
Why would this script be writing over existing folders?
Thanks
The text was updated successfully, but these errors were encountered:
because of windows/cmake/ninja poor support for long path, Qt needs to be built almost at the root :/
Sorry, something went wrong.
[DEBUG] D:\a_work\1\s\src\vcpkg\install.cpp(567): Why is it also writing to D drive? It does not know what is on D?
I haven't worked with vcpkg before, but there seems to be a lot of odd activity going on.
Building from C:\temp\B doesn't result in any immediate errors (is vcpkg really so long it hits the 32k path limit?)
While attempting to run in C:\temp\B I do get a different error that on first inspection doesn't appear to be path length related.
I think I'll just build the headless versions, I don't care about the GUI implementation with QT anyway.
vcpkgerror.log
No branches or pull requests
Hello,
I tried running the buildscript and it overwrote C:\B\ with QT as part of the process.
This was already in use for something else. Luckily I keep backups.
Why would this script be writing over existing folders?
Thanks
The text was updated successfully, but these errors were encountered: