ESP32 Forum

Hello All,

We are excited to announce the release of Espressif-IDE v3.2.0. This minor release focuses on enhancements to the LSP editor, CMake initialization for newly created projects, support for Eclipse 2024-09, improvements to the ESP-IDF Manager, partitions.csv and nvs.csv models editors, documentation updates, OpenOCD debugging enhancements, and various bug fixes to improve the overall quality of the IDE.

Please check more on this here https://github.com/espressif/idf-eclips ... tag/v3.2.0

Best Regards,
IDE Team

well, had a chance to run it for a while. and it doesn't look so exciting for me

1. bullshitty error messages in very simple and successfully compiled code, cannot get rid of

   

   Espressif-IDE.C errors.png (13.16 KiB) Viewed 7140 times

2. user home folder overbloating with ESP-IDF fragments, ignoring installation folder and 'user.home' JVM option user provided.
3. poothon installations duplication instead of reusing the provided one.
4. re-downloading and reinstalling of already installed ESP-IDF instance by ESP-IDF Manager, instead of simply using it.
5. blinking tons of windows during project build, really ugly.
6. spawning lots of processes to do a simple task which others spawn 0(zero) processes to do.

   

   Espressif-IDE.process overbloat.png (33.11 KiB) Viewed 7140 times

regarding 5 and 6 there is a couple of special words... there is a bug #1127 where they say

... during build espessif uses shell which uses python which runs esp idf tools which opens another shell to run cmake which generates scripts to be run by ninja which is the actual build system the runs the actual compiler . (and sometimes cmake would also run another python tool on it's own for partition and file managment)...

damn, guys, who designed this?! under what chemicals???
do they truly believe it cannot break somewhere?! IT DOES!

it may work somehow, but it is a structure made entirely of crutches and prostheses - there are TWO build systems used: CMake and Ninja. and you, guys, definitely won't like it, but it's the awful truth: neither x32 STM32s, nor 8x-16x AVRs, nor even stupid and troublesome PICs require TWO build systems at once - they are happy with single one or a compiler + IDE at all!
so, greetings, poothon fans! couple of words for you: "system analysis" - not asking what it means, have you ever hear the term?

listen, guys! it cries out for a complete redesign at the top of its lungs: "please, please, PLEASE implement me properly - i'm already falling apart into hucking pieces!!!"

Hello,

Sorry that things didn’t work as you expected. However, posting something like this won’t help either of us. If you need a solution, I request you to provide detailed information about each issue along with the relevant logs so that we can address your concern promptly.

Thanks.

However, posting something like this won’t help either of us. If you need a solution...

well, can we address the LSP editor fake errors highlighting?
the thing is when clang for simple (only 'main.c') ESP32 Eclipse project is invoked from cmd console, it says nothing but silently generates the 'main.o' - it definitely knows where the 'stdio.h' is.

the installation is fine and ''compile_commands.json' is generated properly. seems to me, there is not so complex issue...

Hello,

I tried with the default project and the hello-world project in Espressif-IDE 3.2.0, but I don’t see any false error markers on the editors. Could you verify the Clangd settings to ensure they are auto-configured correctly? You can check using Preferences >Editor(LSP) > Clangd

I am attaching my settings for reference for ESP32.

my settings:
all paths are correct. please note:

• it's windows, not linux.
• even if "d:\idIoT.Users\KDV\.espressif" is NTFS symlink, clang handles these paths with no problems when invoked by cmd console command.