(removed redundant post)

GNU extensions? You could try to pass "-pedantic" to g++. That would prohibit extensions to the Standard. Ah, ok, Gnu extensions. That makes sense. Thanks for that. I'm not interested in inhibiting the extensions. I was just wanting to understand on what basis the C++17 compiler was allowing a C++2...

I was just puzzling over something... My ESP-IDF v5.0 application is written in C++. In my main CMakeList.txt I have the following settings: set(CMAKE_CXX_STANDARD 17) set(CMAKE_CXX_STANDARD_REQUIRED ON) I added the following statement in my `main.cpp` to check: std::cout << __cplusplus << "\n"; The...

My whole application is in C++. The only thing you need to do is extern the main C entry point since ESP-IDF expects that to be a C function:

Thanks for the details. I also had tried the template code on a couple of online compilers and did not have a problem.

I agree that it may have to do with the context in which it is used, per the link you provided.

Your tasks calls `wiegand_reader_init`. If you create the task twice, it gets called twice with all the same arguments. Is that expected or desirable? And is that function re-entrant?

Version 5 of ESP-IDF moved from gcc 8.4.0 (used in ESP-IDF v4.4) to gcc 11.2.0. The compiler's confused about something. Your error messages point at `event.h` but your link is to `action.h`. Are these the same file with a different name? Or do you have a local `event.h` that includes `action.h`? I ...

What is the use case or scenario for the "cross-coupling" of ESP32 application partitions? If they have a functional dependency, then shouldn't they be all part of the same application? The purpose of the separate OTA applications is to allow upgrading to newer versions, e.g., over the air, so they ...

Can you show the source for `task`? If it's not re-entrant, then it's a problem to call `xTaskCreate` twice with that same task.

I understand that the chip is the heart and soul of the products it is put into. My Desktop computer is similarly built around an Intel chip but it does not use the MAC Address of the Intel chip inside. It uses a Hewlett Packard MAC Address. Was hoping that maybe although the first part of the MAC ...