-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
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
File paths are way too long #33
Comments
Yes, agreed. I also noticed this issue on buildbot recently and had a temporary solution (3d6fa5c). Looking for better ways now. The long path is because both the default Rust Funnily we are in the year of 2019 now, yet still suffer from some limitation from DOS time. MSBuild should really be modernized: dotnet/msbuild#53. |
As a temporary workaround, you can use |
I've merged #38, which will detect whether Ninja exists in To make MSBuild work means to trim down the path. As discussed in #33 (comment), neither the default Rust target directory organization nor the SPIRV-Tools target name is easy to trim down for that purpose. And both of them can change again in the future. |
The existence of this workaround should also be explicitly documented in the |
oh! so it is, foolish me |
The build process should attempt to use shorter paths.
When attempting to build shaderc-rs, @termhn was given the following error
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\VC\VCTargets\Microsoft.CppBuild.targets(321,5): error MSB3491: Could not write lines to file "x64\Release\spirv-tools-spv-amd-shader-explicit-vertex-parameter\spirv-to.8AECBDF2.tlog\spirv-tools-spv-amd-shader-explicit-vertex-parameter.lastbuildstate". The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. [C:\Users\Gray\Code\learn-gfx-hal\target\debug\build\shaderc-ceea3062217d891f\out\build\spirv-tools\source\spirv-tools-spv-amd-shader-explicit-vertex-parameter.vcxproj]
And then it was fixed by just moving up from
C:\Users\Gray\Code\learn-gfx-hal
toC:\dev\learn-gfx-hal
, so you're right on the limit I guess, shouldn't be too hard to cut down some of the wordy stuff.The text was updated successfully, but these errors were encountered: