[Solved] Creating a new ESP-IDF project with led_strip component - errors in Cmakelists.txt

Hello

Starting a project from "examples" containing the led_strip component, everything compiles. The problem occurs when I create a new project and add the same component manually, i.e. I add the following line to Cmakelists.txt
.

The pictures below explain everything. Please don't write "then start with an example what's the problem". What if I want to use two or three components?
.

The sdkconfig for the project is one and is located in the root directory of the project. The file is generated from the Kconfig files of the components. So, did you execute "idf.py menuconfig" before compilation?

ex-or wrote:

did you execute "idf.py menuconfig" before compilation?

.

Yes, it looks the same:
.

EDIT:

I went into the led_strip/main directory copied the Kconfig.projbuild file to the main folder of my project and finally the same options as in the example appeared in sdkconfig. The compilation went.
Terribly non-obvious is all this. They would have done two lines of define at the beginning of the code like they used to and everything would have been clear. But don't you man scratch your head and look for the settings from ws2812 under the heading.... example configuration
And what now I add a second component and where will it have the settings? example configuration2 ? Of course if I make myself such an item....

NIXIE_123 wrote:

I went to the led_strip/main folder copied the Kconfig.projbuild file to the main folder

.
That's not how it works (or at least it shouldn't). The Kconfig files in the main and component folders work independently of each other. When you fire up idf.py mencuconfig, you should see definitions from all the files. Something probably got messed up, maybe the same section name in two different files.

The configuration created by menuconfig, which manifests itself by generating an sdkconfig file in the project root directory, can be extended by the user. That is, in this beautiful configurator displayed by menuconfig, you can have your own elements.
The bugs reported were precisely about the lack of these additional definitions, they were not in the sdkconfig file.
And custom elements in the configurator are done by adding a Kconfig.projbuild file in the source directory with the contents e.g.:
.
In the configurator, there will be a new menu item named MY settings and in the code there will be self defined macros named CONFIG_ + the name from the config field, e.g. CONFIG_STA_WIFI_SSID.

Nothing like a good old #define