In Windows, need support for longer package paths or ability to specify package folder #1010
Closed
3 tasks done
Labels
conclusion: duplicate
Has already been submitted
os: windows
Specific to Windows operating system
topic: infrastructure
Related to project infrastructure
type: imperfection
Perceived defect in any part of project
Describe the problem
My windows user name, "Michael Farrington", is 18 characters long. Windows applications, by default, can only support 260 path characters. Due to long package names, combined with Arduino placing files into %LocalAppData%, makes the maximum path to a library effectively much shorter.
Windows 10 and above now support breaking the 260 character path limit, but applications must be tagged in their application manifest with the "longPathAware" attribute. See this Microsoft Docs link for more information.
I tried creating my own manifest files to the IDE executable, and executables in the arduino-ide-extensions\build folder, but that did not work. I then tried to do the same to the cc1plus.exe ESP32 compiler executables. Nothing worked, and am left unable to compile some projects (using 1.8.19 or 2.0 RC6), unless I create a new windows profile with a shorter username.
Below is an example of the error. The file that it says is not found is indeed in the folder. If I could specify the folder in which to store the packages, I could gain up to 57 extra characters of path length (if I go to the extreme of placing packages in folder "c:\p"). Obviously removing Windows path length limitations by using longPathAware is the better solution, but I imagine that would require support from 3rd-party compilers.
I realize that this is mostly an issue caused by Windows, but allowing users to move the packages folder location would be of great help.
To reproduce
Try to compile a project that includes files with a file path longer than 260 characters.
Expected behavior
All files to be found.
Arduino IDE version
2.0.0-rc6-nightly-20220529
Operating system
Windows
Operating system version
Windows 11 (Version 21H1)
Additional context
No response
Issue checklist
The text was updated successfully, but these errors were encountered: