Skip to content
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

Unity build fails due to too long path hitting Windows path limtis #31

Closed
reneschulte opened this issue Feb 12, 2020 · 3 comments · Fixed by #32
Closed

Unity build fails due to too long path hitting Windows path limtis #31

reneschulte opened this issue Feb 12, 2020 · 3 comments · Fixed by #32
Assignees

Comments

@reneschulte
Copy link
Collaborator

I cloned the repo to:
D:\Git\OpenSource\Microsoft\MixedReality-WorldLockingTools-Unity

Tried to build for UWP which failed building with this unclear error message: DirectoryNotFoundException: Could not find a part of the path "D:\Git\OpenSource\Microsoft\MixedReality-WorldLockingTools-Unity\Assets\MRTK\MixedRealityToolkit.Providers\WindowsMixedReality\DotNetAdapter\Plugins\net46\Microsoft.Windows.MixedReality.DotNetWinRT\Editor\Microsoft.Windows.MixedReality.DotNetWinRT.Editor.asmdef"

Looking at the long path I guessed it could be hitting the Windows path length limit, therefore I moved the project to the root on my D: disk and there it built just fine.

Not sure what can be done here as it seems to come from the MRTK but might be worth to look into. My typical subfolder I tried to use initially is not extraordinary long and I would expect others to run into the same issue.

@wiwei
Copy link

wiwei commented Feb 12, 2020

With the upcoming release, this should be alleviated (i.e. we did some work in MRTK itself to not have such a crazy long path).

That being said, I think that you'll still likely hit this with longer prefix paths to projects, so to some degree having it be closer to root is still probably good to do.

@fast-slow-still fast-slow-still self-assigned this Feb 12, 2020
@fast-slow-still
Copy link
Contributor

Nice detective work, Rene. I will follow up on this. At the very least I can document this in the setup guide to augment the "unclear error message". Thanks!

@reneschulte
Copy link
Collaborator Author

The warning you added seems not to work as expected:
#32 (comment)

Anyhow, no big deal if the MRTK update will solve this anyway.

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 a pull request may close this issue.

3 participants