I have a CMakeLists.txt that works fine with ESP IDF v3.2, but when I try to build it (from clean check-out) with ESP IDF v3.3 I get the following CMake error: $ $IDF_PATH/tools/idf.py build [...] -- Component paths: [...];/home/me/my-project/main [...] -- Component libraries: CMake Error at CMakeLi...

Now that the ESP-IDF is moving away from Make to Ninja (and Clion doesn't support Ninja) do any of the ESP engineers have any tips to get this to work with IDF v4.x+ please? I'm not an ESP engineer, but CMake supports numerous build tools and I'd be very surprised if the ESP-IDF CMake config does s...

Fair enough - my workaround was a consolidation of other comments to support a single client and multiple reconnections. Two unique non-concurrent clients will need a different solution.

blippy wrote: ↑

Tue Sep 17, 2019 8:01 am

meowsqueak wrote: ↑

Mon Sep 16, 2019 11:20 pm

Did you try the PR I linked to? I didn't have any problems with it, but my use case may be different.

Please provide the link, as it's not on this thread.

It is, but here it is again anyway

https://github.com/espressif/esp-idf/pull/3597

blippy wrote: ↑

Mon Sep 16, 2019 5:52 pm

Comments?

Did you try the PR I linked to? I didn't have any problems with it, but my use case may be different.

I think you might be better off just connecting each LED to a GPIO and using interrupts to catch the state changes, and polling to monitor levels. 5 Hz is absolutely nothing to a microcontroller like the ESP32. It would be a lot easier than using RMT! RMT is better suited to fast signals where you n...

As you're probably aware already, that example just looks at a single signal incoming on a single GPI. The main constraint is the size of the RMT buffers - as the GPI is sampled, a new value is added to the RMT buffer. The size of the buffer required is therefore related to the required sample rate,...

Thanks everyone for your help and advice. Just to follow up, I now have it working properly in Linux and on Mac with v3.2. The key points are: Set CMake options to "-DIDF_PATH=..." in Preferences > Build, Execution, Deployment > CMake and add an entry to the Environments table to set IDF_PATH as wel...

One other thing I've noticed and I can't work out if it's CLion or the CMake build system (that CLion is running frequently) that is doing it, but something is regularly touching (or rebuilding) sdkconfig, which causes the non-cmake system (which I run alongside CLion because I prefer the 'make flas...

Thanks for the reply. I'm also having some trouble with it, although I'm only trying to build IDF examples and my own projects at the moment. I've written a bit about my troubles here: viewtopic.php?f=13&t=11280