0

When when I have long paths in my project (250+ characters), when I trigger my makefile it can't find the include files.

Is there a way to fix this instead of renaming folders to decrease path length?

Also if my long directory is E:\longpanth\includes and my makefile can't find it. How come if I cd E:\longpanth in CMD it finds the directory correctly, could it be something else than CMD, like make.exe or something?

Note: I'm on windows 10 and I use CMD to trigger my makefile

Stuggi
  • 3,366
  • 4
  • 17
  • 34
Kerdany
  • 1
  • 1
  • [About the \\?\ prefix](https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#namespaces): _if the file system supports large paths and file names, you can exceed the [MAX_PATH limits](https://docs.microsoft.com/en-gb/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN#maximum-path-length-limitation) that are otherwise enforced by the Windows APIs._ – JosefZ Apr 06 '20 at 17:07
  • @JosefZ I tried adding it but still didn't work – Kerdany Apr 06 '20 at 21:37
  • Check if the file system supports large paths and file names by running following commands from an open cmd: `reg query "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" -v LongPathsEnabled` and `reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects" -v LongPathsEnabled -S`. BTW, I'd prefer shortening project paths to a _reasonable_ length:) – JosefZ Apr 06 '20 at 22:30
  • @JosefZ Yes, I tried it but still doesn't work, the point is when I cd E:\longpanth in CMD it finds the directory correctly, could it be something else than CMD, like make.exe or something? – Kerdany Apr 08 '20 at 14:03

0 Answers0