Skip to content

build.rs: workaround for windows/vulkan filetracker errors #767

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

Conversation

AsbjornOlling
Copy link
Contributor

@AsbjornOlling AsbjornOlling commented Jul 8, 2025

Because of the recent changes (around ~may 14th) to llama.cpp's cmake stuff around vulkan-shaders-gen, it's very easy to create paths longer than the maximum allowed on windows, when building crates that depend on llama-cpp-rs on windows that use the vulkan backend.

Yes, it is possible to change the maximum path length on windows (e.g. the windows-latest github actions runner already does this, afaik), but it seems like there are some quirks in MSBuild's FileTracker, that makes it not respect the maximum file path set in the windows registry. I'm by no means a windows expert, but it seems like the rabbit hole goes deep here. (e.g. issue 53 on dotnet/msbuild)

To work around this issue, I added some configuration specifically for windows+vulkan builds, that disables the msbuild filetracker thingy. This means that windows vulkan builds re-build things more frequently than strictly necessary - but at least it no longer crashes with (very non-descriptive) errors caused by long paths.

It's kind of a hack, but it makes windows+vulkan builds work in github actions again.

@MarcusDunn MarcusDunn merged commit a877425 into utilityai:main Jul 9, 2025
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy