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
Regarding to historical reason, path that exceeds 260 characters are not directly supported on Windows.
Ninja now uses ANSI instead of Unicode style on some of Windows APIs. This could lead to "ERROR 206" (The filename or extension is too long.).
Ninja fails when calling GetFullPathNameA etc on a file that is deeply nested or has long generated name. For now, the only solution is reducing directories nested for the project to bypass. But it doesn't solve this issue if Ninja comes to a file that really has a 260 characters long name.
For example, the following error was generated when I tried to compile V8:
GetFullPathNameA(gen/third_party/blink/renderer/bindings/modules/v8/v8_union_gpucanvascontext_imagebitmaprenderingcontext_offscreencanvasrenderingcontext2d_webgl2renderingcontext_webglrenderingcontext.h): The file name or extension is too long
So should we migrate all ANSI styled call to the Unicode version?
The text was updated successfully, but these errors were encountered:
Regarding to historical reason, path that exceeds 260 characters are not directly supported on Windows.
Ninja now uses ANSI instead of Unicode style on some of Windows APIs. This could lead to "ERROR 206" (The filename or extension is too long.).
Ninja fails when calling
GetFullPathNameA
etc on a file that is deeply nested or has long generated name. For now, the only solution is reducing directories nested for the project to bypass. But it doesn't solve this issue if Ninja comes to a file that really has a 260 characters long name.For example, the following error was generated when I tried to compile V8:
So should we migrate all ANSI styled call to the Unicode version?
The text was updated successfully, but these errors were encountered: