LTO build failure on Windows (for ESP32-S3, LovyanGFX) CreateProcess: No such file or directory #7892
Replies: 3 comments 2 replies
-
It doesn't actually solve the issue as the firmware.bin gets ~300 kB larger. It's just a workaround for the limitations of the restricted linker command line (< 32 kB) on the Windows platform. |
Beta Was this translation helpful? Give feedback.
-
I didn't know that. |
Beta Was this translation helpful? Give feedback.
-
On Windows you can use WSL2 and the vscode Remote Development plugin which gives you a smooth transparent link to the Linux world with all benefits including source level debugging for native. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
When building the Meshtastic project on Windows (10 64-bit) with PlatformIO, using ESP32-S3 environments (including LovyanGFX variants), the build fails with the following error:
Environment:
OS: Windows 10 64-bit
PlatformIO Core: 6.1.19a2
Toolchain: xtensa-esp32s3-elf@8.4.0+2021r2-patch5
Project path: deep folder structure (e.g., /variants/MCU/DEVICE/...)
VSCode + PlatformIO extension
What I tried:
Moving .platformio to a shorter path (d:\pio)
Deleting the project .pio build folder
Fresh clone of the repository
Comparing local build with GitHub Actions build (all toolchains and frameworks matched)
What solved the issue:
Adding the following to platformio.ini successfully allowed the build to complete:
Notes:
The project builds fine on GitHub Actions, so this appears to be a Windows-specific LTO/path issue.
It may be helpful to document or include platform-specific build flags for Windows S3 environments to prevent similar issues for other contributors.
Beta Was this translation helpful? Give feedback.
All reactions