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
Installing with H:/Unity_Downloads/2019.4.0f1/android-ndk-r19-windows-x86_64.zip
error: No such file or directory @ rb_sysopen - D:/Unity_2019.4.0f1/Editor/Data/PlaybackEngines/AndroidPlayer/NDK/android-ndk-r19/sources/cxx-stl/llvm-libc++/test/std/thread/thread.mutex/thread.mutex.requirements/thread.sharedtimedmutex.requirements/thread.sharedtimedmutex.class/try_lock_until_deadlock_bug.pass.cpp. Use --trace to view backtrace
The text was updated successfully, but these errors were encountered:
Issue Checklist
u3d --help
Issue Description
I think the problem has to do with that.
268 characters
D:/Unity_2019.4.0f1/Editor/Data/PlaybackEngines/AndroidPlayer/NDK/android-ndk-r19/sources/cxx-stl/llvm-libc++/test/std/thread/thread.mutex/thread.mutex.requirements/thread.sharedtimedmutex.requirements/thread.sharedtimedmutex.class/try_lock_until_deadlock_bug.pass.cpp
However, if I decompress it by hand, it does work. That is, I take the downloaded zip with u3d and unzip it into:
D:/Unity_2019.4.0f1/Editor/Data/PlaybackEngines/AndroidPlayer/NDK/
So I understand that the MAX_PATH problem has to do with u3d directly.
In a .NET application it is enabled in the following way, I don't know in Ruby what it will be:
https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#enable-long-paths-in-windows-10-version-1607-and-later
I tried enabling "Enable Win32 long paths" option but it still doesn't work with u3d
I don't know if this would help:
https://stackoverflow.com/questions/57317695/writing-to-an-external-file-with-long-file-name-with-ruby-file-open#comment101133540_57317980
https://www.ruby-forum.com/t/no-such-file-or-directory-bug-due-to-filepath-length/126851/4
In the section "Maximum Path Length Limitation" they also speak in the official documentation of the workaround with Unicode
https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN
The text was updated successfully, but these errors were encountered: