-
-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The filename or extension is too long #2368
Comments
I found out that compile command length for the This was much longer than the IDE generates, which is 27206 bytes. And if I truncate all data path from both commands, there length were almost same(18671 for IDE, 18282 for arduino-cli). The major difference was just a data path length. I moved the project directory directly under C:\ and it compiles normally. BTW, I think this problem needs some robust solution instead of depending on absolute path length of I didn't take a closer look at it, but I thought #839 (comment) was a solution for diminishing commands length. But it didn't worked at all, including insert content directly into |
I have the same problem with both Arduino Legacy IDE and Arduino IDE V2 on Windows 10 when using the latest |
Describe the problem
In Windows, I cannot compile a sketch with a following error.
It seems like that
xtensa-esp32-elf-g++.exe: The filename or extension is too long.
is the problem.I found some related issues #839 and #961.
I think this problem is fixed at around
0.14
according to the issues above, but I'm experiencing the problem in0.34
.platform.local.txt
at #839 (comment) did not worked.To reproduce
The default ESP32 example sketches instead of mine have same problem, too.
arduino-cli.yaml
Expected behavior
A normal compilation as IDE does, instead of
The filename or extension is too long
error.Arduino IDE 2.2.1 compile output
arduino-cli 0.34 compile output
Arduino CLI version
arduino-cli.exe Version: nightly-20231013 Commit: 3a2f9f1 Date: 2023-10-13T01:28:47Z
Operating system
Windows
Operating system version
Windows 11 Pro 22H2
Additional context
No response
Issue checklist
The text was updated successfully, but these errors were encountered: