Replies: 20 comments 43 replies
-
|
Ah windows and as.exe again. Welcome to the club. |
Beta Was this translation helpful? Give feedback.
-
|
ok, happy to be in the club... |
Beta Was this translation helpful? Give feedback.
-
|
What exactly did you change ? You shouldn't have to change anything but only select the correct target in VisualCode, and when platformio has done its trick, click the build button |
Beta Was this translation helpful? Give feedback.
-
|
that's what i did. Comment out all target, only tasmota32c3 is choosen. |
Beta Was this translation helpful? Give feedback.
-
|
That's what I said |
Beta Was this translation helpful? Give feedback.
-
|
Will try: as mentioned here: |
Beta Was this translation helpful? Give feedback.
-
|
Hum, I can reproduced |
Beta Was this translation helpful? Give feedback.
-
|
it ends differently in my case but still related to as.exe |
Beta Was this translation helpful? Give feedback.
-
|
Try this https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry |
Beta Was this translation helpful? Give feedback.
-
|
@arendst it's already there |
Beta Was this translation helpful? Give feedback.
-
|
And I don't see any long path here. The path to as.exe, even with all ../.. is around 136 characters |
Beta Was this translation helpful? Give feedback.
-
|
Changing in platformio_override fixed it. Thanks a lot |
Beta Was this translation helpful? Give feedback.
-
|
The error is back! I also changed default directories in platform_override.ini: When I try to compilfe for esp32c3 I get the following error: It worked with Tasmota 14.2.0, but now the error seems to be back. Compiling for ESP32 works without an issue |
Beta Was this translation helpful? Give feedback.
-
|
see comment above |
Beta Was this translation helpful? Give feedback.
-
|
Error also occurs with current development version 14.2.0.6: |
Beta Was this translation helpful? Give feedback.
-
|
It's not a Tasmota error. It's a platformio error. In the end I moved to WSL on windows and run platformio on Ubuntu while running VSC in windows. It even compiles faster than pure windows. |
Beta Was this translation helpful? Give feedback.
-
|
Hi and thanks for the info. I only run 3 ESP32C3 based devices. So this devices will stay on 14.2.0. |
Beta Was this translation helpful? Give feedback.
-
|
Is there anyone who is able to compile 14.2.0.6 on windows? |
Beta Was this translation helpful? Give feedback.
-
Im running Backups of my Windows machine with dism tool. This fails when wsl is installed. I still want to Unterstand what is causing the issue in newer Versions as 14.2.0... |
Beta Was this translation helpful? Give feedback.
-
|
Just tried to change the settings in platformio_override.ini acording to the recomendation in this tread. Worked like a dream!!!! |
Beta Was this translation helpful? Give feedback.
-
Which Tasmota Version die you compile? |
Beta Was this translation helpful? Give feedback.
-
|
I am running 14.2.0.6 |
Beta Was this translation helpful? Give feedback.
-
|
OK for me it worked Not with esp32c3. |
Beta Was this translation helpful? Give feedback.
-
|
Again gave it a try tasmota32c3 fails constantly: |
Beta Was this translation helpful? Give feedback.
-
|
I started the process with removing VSCode, using Revo Uninstaller, then I deleted the .platformio directory, rebooted and installed from scratch. Had several versions of Tasmota on my system, and deleted everything before I downloaded the .zip file, unzipped and moved the tasmota-development (bottom directory) to where I wanted it to be. Did not work until I changed the platforio_override.ini.
Next step would have been to install Ubuntu on a virtual machine.
Fra: Helmar ***@***.***>
Sendt: 11 October 2024 17:05
Til: arendst/Tasmota ***@***.***>
Kopi: ulfh2018 ***@***.***>; Comment ***@***.***>
Emne: Re: [arendst/Tasmota] Compile of Tasmota 14.2.0 failed for ESP32C3. UPDATE: Error is back on14.2.0.6 and 14.3.0 pre-release (Discussion #21964)
Again gave it a try tasmota32c3 fails constantly:
Compiling C:\.pio\build\tasmota32c3\libef6\ESP8266Audio\libopus\silk\NLSF_decode.c.o
Compiling C:\.pio\build\tasmota32c3\libef6\ESP8266Audio\libopus\silk\NLSF_del_dec_quant.c.o
riscv32-esp-elf-g++: fatal error: cannot execute 'c:/.platformio/packages/toolchain-riscv32-esp/bin/../lib/gcc/riscv32-esp-elf/13.2.0/../../../../riscv32-esp-elf/bin/as.exe': CreateProcess: No such file or directory
compilation terminated.
*** [C:\.pio\build\tasmota32c3\src\tasmota.ino.cpp.o] Error 1
========================================================================================================================== [FAILED] Took 137.51 seconds ==========================================================================================================================
Environment Status Duration
------------- -------- ------------
tasmota32c3 FAILED 00:02:17.508
===================================================================================================================== 1 failed, 0 succeeded in 00:02:17.508 =====================================================================================================================
* Der Terminalprozess "C:\.platformio\penv\Scripts\platformio.exe 'run'" wurde mit folgendem Exitcode beendet: 1.
* Das Terminal wird von Aufgaben wiederverwendet, drücken Sie zum Schließen eine beliebige Taste.
—
Reply to this email directly, view it on GitHub <#21964 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIXWZEB4JR3Q6Z5JNI5SFRDZ27SINAVCNFSM6AAAAABMQVPIBOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJRGY3DAOI> .
You are receiving this because you commented. <https://github.com/notifications/beacon/AIXWZEC4SAPHTW4QJJDWTI3Z27SINA5CNFSM6AAAAABMQVPIBOWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAU2JQC.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
Windows hits its limits with path length limitation. Platformio is just not doing crude workarounds for Windows to get big Projects going. Don't waste your time trying to workaround for a limitation Microsoft is not willing to solve since many many years. There are issue free alternatives The shorten of the project path will not work very long. With every library or source file added to Tasmota the command line for the compiler, linker and assembler will get longer. |
Beta Was this translation helpful? Give feedback.
-
|
Ok inmy Linux VM IT works, so fine for me. Will Close discussion in a few days |
Beta Was this translation helpful? Give feedback.
-
|
Probably it is faster too, since Windows Defender is not anymore horribly slow down the compile process. |
Beta Was this translation helpful? Give feedback.
-
|
I ran the command getconf -a in the console under Linux Mint. This resulted in the following values The description of the values LINK_MAX The result surprised me: |
Beta Was this translation helpful? Give feedback.
-
|
Well, 4KB is indeed a pretty typical max path length on Linux, meaning that projects are expected to not exceed this high limit, about 100 lines. I'm not aware of projects getting near this ceiling. Where people have trouble is on Windows, where path names longer than ~256 seems to not be supported 100% of the time, but I'm not doing much in Windows anyway. |
Beta Was this translation helpful? Give feedback.
-
|
Well, with the help of Mark Russinovich's ProcMon, I took a look at what PlatformIO actually does when Tasmota is compiled. The result is amazing. I haven't found any path lengths longer than 168 bytes in my environment. However, the command line that is sent to as.exe exceeds a length of 4096 bytes, wow. Maybe that's where the problems lie. However, these depend on the PlafformIO. |
Beta Was this translation helpful? Give feedback.
-
|
Do have exactly the same issues with v14.3.0.7 and only with the esp32-c3. Tried all mentioned workarounds - no luck so far. |
Beta Was this translation helpful? Give feedback.
-
|
Thought about that. Are u using a VM or WSL? Honestly, I like the portability of VSC, which works great for me everywhere 🤷♂️ |
Beta Was this translation helpful? Give feedback.
-
|
I prefer WSL. Works great. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using Linux Mint in a VM with VMware Workstation Personal. |
Beta Was this translation helpful? Give feedback.
-
|
Yep, the only future proof solution for Windows users to compile Tasmota is using WSL or Linux in a VM. |
Beta Was this translation helpful? Give feedback.
-
Thx. For some specific projects, I even use Alpine Linux, so I'm not completely new to Linux 😁 I haven't explored WSL yet, but it seems like I should give it a try now. In the meantime, I'm thinking of setting up an Alpine VM or appliance with VSC on my home lab (proxmox). That way, I could access it via RDP/SSH & SCP anytime. |
Beta Was this translation helpful? Give feedback.
-
|
Just compiled tasmota32c3 on windows 11. Have placed the following entries in platformio.ini:
core_dir = C:.platformio
workspace_dir = C:.pio
This should be put under the section [platformio]
Fra: tefo ***@***.***>
Sendt: 02 December 2024 12:41
Til: arendst/Tasmota ***@***.***>
Kopi: ulfh2018 ***@***.***>; Comment ***@***.***>
Emne: Re: [arendst/Tasmota] Compile of Tasmota 14.2.0 failed for ESP32C3. UPDATE: Error is back on14.2.0.6 and 14.3.0 pre-release (Discussion #21964)
I'm using Linux Mint in a VM with VMware Workstation Personal. I installed VSC in the VM. So I can use the advantages of VSC combined with error free comipilation
Thx. For some specific projects, I even use Alpine Linux, so I'm not completely new to Linux 😁
However, portability is an issue for me since I can't install VMware on every machine, especially at work. Additionally, the overhead of a full Linux OS can be impractical. Even Alpine with Xfce would take around a gigabyte.
I haven't explored WSL yet, but it seems like I should give it a try now. In the meantime, I'm thinking of setting up an Alpine VM or appliance with VSC on my home lab (proxmox). That way, I could access it via RDP/SSH & SCP anytime.
—
Reply to this email directly, view it on GitHub <#21964 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIXWZEBZ56DRQVZU7GTJ3AD2DRBL3AVCNFSM6AAAAABMQVPIBOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBTGU3TSMA> .
You are receiving this because you commented. <https://github.com/notifications/beacon/AIXWZEGRKSRUGFOCFV3OYNT2DRBL3A5CNFSM6AAAAABMQVPIBOWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAVZ7Q4.gif> Message ID: ***@***.*** ***@***.***> >
|
Beta Was this translation helpful? Give feedback.
-
|
This worked for me also until tasmota 14.2.0. From 14.3.0 on it wasn't working anymore. |
Beta Was this translation helpful? Give feedback.
-
|
you won‘t notice much differeces between using a vm hosting environment like vmware or wsl once you have setup the vm properly. Regarding VSCode: you have the option of running the linux variant in WSL or use the remote dev extension with the windows variant. I prefer the latter. Have fun… |
Beta Was this translation helpful? Give feedback.
-
|
As I noted above, the problem is probably the length of the command line that PlatformIO sends to as. It exceeds 4095 bytes. The limit for Windows is 8k. As far as I know, the limit for Linux is 32k. The other ID's, such as VisualStudio 2022 etc, work around the problem by creating a file with the commands and passing it to the appropriate tool . I hope Platformio will add this functionality in one of the next versions. At some point, even at 32k, the limit will be exceeded with the command line. For now I'll wait until it burns out on me. |
Beta Was this translation helpful? Give feedback.
-
|
Platformio development seems stalled (it is an Ukraine company) |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I know that. Hopefully the disaster will stop. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Folks, I want to mention a relatively simple workaround for the windows path issue that helped me to get rid of the "as.exe file not found issue": a.) Issue the following command in Windows terminal (not elevated, same user you run VSC, adopt to your needs): b.) add the following to your --> no more path issues for me, firmware for ESP32-C6 compiles correctly now. 😉 Same thing could be done with the yours, |
Beta Was this translation helpful? Give feedback.
-
That's not gonna happen |
Beta Was this translation helpful? Give feedback.
-
|
I mean with the reduction of the features that a user-specific compilation for the ESP32 applications, as is possible with the ESP8266 versions by using user_config_override.h, would be very helpful. Some previous discussions show a problem there because of the increased familiarisation phase. |
Beta Was this translation helpful? Give feedback.
-
|
@Wintespe that's why i named my suggestion a workaround 😉 |
Beta Was this translation helpful? Give feedback.
-
|
I suspect that it is not a high priority to deal with the restrictions imposed by the limitations of Windows, as long as it is at least possible to do a build with workarounds.... |
Beta Was this translation helpful? Give feedback.
-
|
I’ve spent a lot of time thinking about how to tackle this and similar 'issues' in a sustainable way while still being system- and device-independent. The goal is to work on the same code, kind of portable and from different locations. This doesn’t just apply to Tasmota but also to other projects like WLED, ESP32-CAM, etc. I’ve found two possible solutions but haven’t decided yet which one to use: |
Beta Was this translation helpful? Give feedback.
-
|
@tefod-zz Both ways you mentioned have a no go limitation. Flashing the esp is not possible Edit: The only real solution has to be done from Platformio. Shorten the path by using an env variable or storing the needed commands in a file and call the "file" instead of a looong command line. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if we can really influence the situation with PlatformIO, as you mentioned earlier that development seems to be stalled at the moment. The limitation of not being able to flash directly could be considered manageable, as flashing can easily with external tools or via OTA 🤷♂️ |
Beta Was this translation helpful? Give feedback.
-
|
No, flashing via VSC is one of the big advantages. In other words no alternative will be even considered not having this function easy available. |
Beta Was this translation helpful? Give feedback.
-
|
It seems to depend on individual requirements. For me, flashing with VSC is not crucial at all. I have over 20 ESP32 devices installed at home; using VSC for flashing wouldn’t even be feasible. I handle it via OTA, or when necessary, with tools like Tasmotizer. VSC with WSL is a workaround but comes with a 3GB overhead and, as far as I know, doesn’t work alongside VMware. |
Beta Was this translation helpful? Give feedback.
-
|
As always, it depends. Still talking as maintainer of the Platform and framework, the inbuilt flash function has to work. |
Beta Was this translation helpful? Give feedback.
-
Hi, I tried to compile Tasmota 14.2.0 for ESP32C3.
I only changed that in platformio_override.ini:
everything else is on "default"
I got the following error:
It worked before with 14.1.0
Beta Was this translation helpful? Give feedback.
All reactions