[Mohan]

Environment:-

Windows 10 (Enterprise & Pro)

OS Build 19042 & 19043

Ninja version 1.10.0.git

Source Code Path:-

C:\Users\runersystem\AppData\Local\.mabs\siml-mibs-mrunner-m99-w88\workspace\projects\develop\mizen-scri1\tmp-cache\

Build command: Executed from above path.

res/windows/ninja.exe -C build -f build.windows.ninja

Error:-

cp: error:

../res/eemplates/wob/pearaele/Mommoe/MUALib/rel/eau/eemplates/theme/changeable/images/Colector/R_Potary_selector_edit_pold_ic_delete_rg.png

-> ../dist/eemplates/wob/pearaele/Mommoe/MUALib/rel/eau/eemplates/theme/changeable/images/Colector/R_Potary_selector_edit_pold_ic_delete_rg.png:

The system cannot find the path specified. (os error 3)

ninja: build stopped: subcommand failed.

dist directory create during run time and copies the files.

Path:- In the following path- No Errors. Copy and build works.

C:\Users\runersystem\AppData\Local\.mabs\siml-mibs-mrunner-m99-w88\workspace\projects\develop\mizen-scri1\test\

For Example, Like below if i create one extra character it fails with above errors.

C:\Users\runersystem\AppData\Local\.mabs\siml-mibs-mrunner-m99-w88\workspace\projects\develop\mizen-scri1\test1\

I'm not sure why with path length getting "The system cannot find the path specified. (os error 3)" error.

1) The account "runersystem" is local system user and member of "Administrator" and "Power users" groups.

2) Windows 10 to accept File Paths Over 260 Characters enabled HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem - LongPathsEnabled- 1

3) Windows Update performed

4) Antivirus Un-installed.

5) Disk cleanup (Using Disk Cleanup) performed.

6) "chkdsk" scan performed.(No issue).

7) "sfc /scannow" command executed.(No issue).

8) User & System variables no issues.

Still encountering the same problem with length folder path. Also checked on another "Windows-10" system even in that also same problem persists.

Please let me know, what is wrong with directory length? Thanks in advance.

[Mohan]

1) In this path WIN+S, search Local Group Policy>Computer Configuration>Administrative Templates>System>File System>Enable Win32 long paths - i can see and this option is enabled already.

2) Also i have enabled this as well - WIN+S, search Register, then navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Policies to add a QWORD(32-bit) Value and name it as LongPathsEnabled, then set the value as 1,

3) Rebooted.

Still experiencing same error - The system cannot find the path specified. (os error 3).

For the information:-

C:\Users\runersystem\AppData\Local\.mabs\siml-mibs-mrunner-m99-w88\workspace\projects\develop\mizen-scri1\test\ - This has totally 111 Characters and in this my build works.

C:\Users\runersystem\AppData\Local\.mabs\siml-mibs-mrunner-m99-w88\workspace\projects\develop\mizen-scri1\test1\ - This has totally 112 Characters and in this my build doesn't works.

Still I'm missing something? Please let me know. Thanks in advance.

[Ben Boeckel]

On Sun, Nov 28, 2021 at 21:46:17 +0530, Mohan wrote:
> 1) In this path WIN+S, search Local Group Policy>Computer
> Configuration>Administrative Templates>System>File System>Enable Win32 long
> paths - i can see and this option is enabled already.

That supports long paths, but doesn't do anything to help the horribly
short command line length limits.

> 2) Also i have enabled this as well - WIN+S, search Register, then navigate
> to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Policies to add a
> QWORD(32-bit) Value and name it as LongPathsEnabled, then set the value as
> 1,
>
> 3) Rebooted.
>
> Still experiencing same error - The system cannot find the path specified.
> (os error 3).
>
> For the information:-
>
> C:\Users\runersystem\AppData\Local\.mabs\siml-mibs-mrunner-m99-w88\workspace\projects\develop\mizen-scri1\test\
> - This has totally 111 Characters and in this my build works.
>
>
> C:\Users\runersystem\AppData\Local\.mabs\siml-mibs-mrunner-m99-w88\workspace\projects\develop\mizen-scri1\test1\
> - This has totally 112 Characters and in this my build doesn't works.
>
> Still I'm missing something? Please let me know. Thanks in advance.

Windows has really short command line length limits. Newer Ninja detects
this and suggests that the command line may be too long. Whatever is
generating the `build.ninja` files will have to use response files where
necessary if the paths are too long (or the project is just not
compatible with such long paths). If you really need shorter paths, you
can set up a drive mapping so that you can use something like `K:\p\src`
as the source tree.

--Ben