Since you specified that '${CMAKE_HOME_DIRECTORY}/components/i2c_self_test' is a component directory, the IDF build expects, Kconfig.projbuild to be there, i.e. '.../i2c_self_test/Kconfig.projbuild'. I guess the thing here is that in the examples, 'i2c_self_test' is not a component, it is a project ...

CMake automatically does parallel builds. Even faster build times can be achieved by using ccache. This can be done by: 1. passing argument `--ccache` to idf.py everytime you build 2. set CCACHE_ENABLE=1 before project() call in project CMakeLists.txt like so ... set(CCACHE_ENABLE 1) project(...) Yo...

Sharing my experience as well. I've had the same error as you did. Having ESP-IDF environment variables (IDF_PATH, addition of toolchain to PATH) in ~/.profile made import of CMake projects seamless for me.

Ok, so EXTRA_COMPONENT_DIRS is depricated? Will try this out this evening. So one of the changes is we separated factored out a 'core build system'. This 'core build system' is the one defined in https://github.com/espressif/esp-idf/blob/master/docs/en/api-guides/build-system-cmake.rst#esp-idf-cmak...

Apologies in the late response. Do you have a summary of changes made? The main things are: - Formalize an API (properties + commands) for implementing projects on top of ESP-IDF build system. This is documented in the 'ESP-IDF CMake Build System API' section of build-system-cmake.rst (https://githu...

Hi urban,

The fix has already been merged for master: https://github.com/espressif/esp-idf/co ... 75a1c0be2a. It might take some time to get it backported to v3.3. In the meantime, you can redo the changes in the linked commit on your custom bootloader.

Renz

Hello everyone, We have been making changes to ESP-IDF CMake build system internals for the 4.0 release to better facilitate the some of the use cases that have been mentioned in this thread. The bulk of these changes has already been pushed to Github. Please take a look at the latest master if you ...

Hi Urban, I'm assuming you haven't done heavy modifications to the project_include.cmake, since the problem occurs even if we just take a copy of the original component and plop it in the components folder. The problem lies with bootloader subproject build still using the original copy of the compon...