Hi,

I'm having a very similar issue with a Fysetc E4 board https://github.com/FYSETC/FYSETC-E4/tree/main , and just yesterday I fried the second board in a short time... I also was trying to control the motors when at some point the board stopped responding and now 3.3V is shorted to GND on the ...

If you want to use your own policy, just add #pragma which disables warnings.
Since you are going to fix them anyway, this temporary solution (#pragma) is ok.

In general, if you are developing something using SDK the general rule is to use their constraints. Probably they are there for a reason ...

Seems quite basic to me, but it will fail to build. And if you're telling me that I have to change my policy to match IDF's, then sorry but i strongly disagree, and there's nothing to discuss further unless you bring a real solution.

Bye
Andrea


You forgot to add "#" at the very beginning ...

Solved... the issue was that when you #define NO_GLOBAL_INSTANCES then the global extern WiFiClass WiFi is not declared, but other classes rely on that global to be available.

Declaring a global WiFi solves the issue... not sure why it didn't throw an error during compilation but anyway now it ...

Hi,

I had a code that worked as expected in esp-idf v5.1.6, but after upgrading to v5.5.1 doesn't connect any longer to my wifi network... here is the log:


I (1569) wifi:wifi driver task: 3ffd0b8c, prio:23, stack:6656, core=0
I (1589) wifi:wifi firmware version: 14da9b7
I (1589) wifi:wifi ...

but there's no reason on earth why I should follow ESP's warning/error policy and not my own.

Some might see being compatible with the SDK you're using as a reason. Some might say that there's no reason on earth why your code should be producing warnings in the first place.

Being compatible ...

I suggest to fix the cause(s) of the warning(s)/error(s) instead of disabling it (e.g. https://twdev.blog/2024/07/cpp_overloaded_virtuals/).

If you "need" a certain construct which gives a warning/error, you can selectively control the warning behavior for that piece of code via gcc's Diagnostic ...

Hi,

I'm having this extremely annoying issue where esp-idf forces down my throat its compiler warnings as errors. In the specific case I have

error: 'virtual void Motor::run()' was hidden [-Werror=overloaded-virtual=]

I tried to disable this behaviour (together with setting my own flags) in the ...

Hi,

I'm programming an esp32 board with C++/FreeRTOS and so far things are progressing; however there's one thing that seem to cause all sort of issues like stack corruption and guru meditations, and that is std::string.

I read that rising the stack size could maybe help. but how do I do that for ...