Kconfig.projbuild

[profjmer]

Do the Sming build system use Kconfig.projbuild to configure sdk-menuconfig.
If yes where should I put this file

[mikee47]

See SDK_CUSTOM_CONFIG (https://sming.readthedocs.io/en/latest/_inc/Sming/Arch/Esp32/README.html#envvar-SDK_CUSTOM_CONFIG)

Custom SDK settings for a project can be defined in a separate file and setting this value to the location, relative to the project source root directory.

These will be added to the default SDK settings.

To make the settings current, you must run make sdk-config-clean. This will discard any changes made via make sdk-menuconfig.

[mikee47]

Also see https://sming.readthedocs.io/en/latest/_inc/Sming/Arch/Esp32/Components/esp32/index.html#background

[profjmer]

Let's suppose that I have a Kconfig.projbuild in the root of my project. Then I must set SDK_CUSTON_CONFIG with (first attempt SDK_CUSTOMCONFIG = Kconfig.projbuild, second attempt SDK_CUSTOMCONFIG =./Kconfig.projbuild) Then execute make sdk-config-clean Then where the updated menu should appear ( menuconfig or sdk-menuconfig) ? Should I change the name of the configuration file ? What am I doing wrong ? One more time thanks for your help

…

On Sat, Feb 17, 2024 at 4:52 PM Mike ***@***.***> wrote: Also see https://sming.readthedocs.io/en/latest/_inc/Sming/Arch/Esp32/Components/esp32/index.html#background — Reply to this email directly, view it on GitHub <#2718 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMZXFYXFZAWFZGCRV27I3ULYUERCVAVCNFSM6AAAAABDNRI2BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGM4TSOJRGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mikee47]

This should work:

make SDK_CUSTOM_CONFIG=Kconfig.projbuild
make sdk-config-clean
make

Note: You'd typically add SDK_CUSTOM_CONFIG=Kconfig.projbuild to your project's component.mk file. Remember to run make config-clean if it doesn't take.

Assuming a debug build for esp32 variant the config used can be found in $(SMING_HOME)/Arch/Esp32/Components/esp32/project/esp32/debug/sdkconfig.defaults. This is a composite of all the sming-defined defaults with your Kconfig.projbuild settings appended.

The IDF tools creates the sdkconfig in the same directory. When you run make sdk-menuconfig it is this file which gets edited. Running make sdk-config-clean removes both of these files.

[profjmer]

I tested the modification of a menu in ESP-IDF (peripherals/rmt/ir_protocols) with the Kconfig.projbuild provided. It worked under ESP-IDF idf.py menuconfig
I copied the Kconfig.projbuild from the example in BASIC_BLINK.
I proceeded according to your instructions and the compiler complains that all the lines are malformed.
Here are some lines
/tmp/confgen_tmpnkw6klgx:87: warning: ignoring malformed line 'menu "Example Configuration"'
/tmp/confgen_tmpnkw6klgx:88: warning: ignoring malformed line 'choice EXAMPLE_IR_PROTOCOL'
/tmp/confgen_tmpnkw6klgx:89: warning: ignoring malformed line 'prompt "Infrared Protocol"'

Does it work on your end ?

[mikee47]

Sorry, I've got the wrong end of the stick. I found the example file you mention in IDF version 4.4. Copy that as Kconfig to the project root, then run make menuconfig.

[profjmer]

Perfect
Thanks again

[profjmer]

Now I guess. application.app needs an #include directive to find the variables. In my case, #include "sdkconfig.h" includes something irrelevant from another project (I tried also #include "../Kconfig) without success. I can't see any sdkconfig.h generated in my project. compiler complains about not able to resolve pinMode(EXAMPLE_RMT_RX_GPIO, OUTPUT), or pinMode(CONFIG_EXAMPLE_RMT_RX_GPIO, OUTPUT); error: 'EXAMPLE_RMT_TX_GPIO' was not declared, or error: 'CONFIG_EXAMPLE_RMT_TX_GPIO' was not declared, What should I include in application.app to resolve this ?

…

On Sun, Feb 18, 2024 at 8:01 AM Mike ***@***.***> wrote: Sorry, I've got the wrong end of the stick. I found the example file you mention in IDF version 4.4. Copy that as Kconfig to the project root, then run make menuconfig. — Reply to this email directly, view it on GitHub <#2718 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMZXFYVNXK7GDSPTYCKTD53YUH3T7AVCNFSM6AAAAABDNRI2BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGMYTSNJYGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mikee47]

These variables are available in makefiles but not in code (no .h file is generated). If you require values in code then you might add something like this to your component.mk file:

GLOBAL_CFLAGS += \
	-DEXAMPLE_IR_PROTOCOL_NEC=$(EXAMPLE_IR_PROTOCOL_NEC) \
	-DEXAMPLE_IR_PROTOCOL_RC5=$(EXAMPLE_IR_PROTOCOL_RC5) \
	-DEXAMPLE_RMT_RX_CHANNEL=$(EXAMPLE_RMT_RX_CHANNEL) \
	-DEXAMPLE_RMT_RX_GPIO=1910$(EXAMPLE_RMT_RX_GPIO) \
	-DEXAMPLE_RMT_TX_CHANNEL=$(EXAMPLE_RMT_TX_CHANNEL) \
	-DEXAMPLE_RMT_TX_GPIO=18100$(EXAMPLE_RMT_TX_GPIO)

[profjmer]

Ok thanks, it's different from ESP-IDF where we only have to add an #include "sdkconfig.h" and prepend variables with CONFIG_

…

On Mon, Feb 19, 2024 at 10:50 AM Mike ***@***.***> wrote: These variables are available in makefiles but not in code (no .h file is generated). If you require values in code then you might add something like this to your component.mk file: GLOBAL_CFLAGS += \ -DEXAMPLE_IR_PROTOCOL_NEC=$(EXAMPLE_IR_PROTOCOL_NEC) \ -DEXAMPLE_IR_PROTOCOL_RC5=$(EXAMPLE_IR_PROTOCOL_RC5) \ -DEXAMPLE_RMT_RX_CHANNEL=$(EXAMPLE_RMT_RX_CHANNEL) \ -DEXAMPLE_RMT_RX_GPIO=1910$(EXAMPLE_RMT_RX_GPIO) \ -DEXAMPLE_RMT_TX_CHANNEL=$(EXAMPLE_RMT_TX_CHANNEL) \ -DEXAMPLE_RMT_TX_GPIO=18100$(EXAMPLE_RMT_TX_GPIO) — Reply to this email directly, view it on GitHub <#2718 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMZXFYVJ4PAA4EEDOWG7FE3YUNYEPAVCNFSM6AAAAABDNRI2BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJSG42DONRSGI> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[mikee47]

If you want to generate a .h file for your project, you can always add the required logic to your component.mk file, run commands manually or suggest a PR to the framework to automate this.

You can generate a header file directly like this:

CONFIG_= KCONFIG_CONFIG=out/Esp32/esp32/debug/kconfig.config /usr/bin/python3 -m genconfig

This will create the file config.h by default. Use --header-path to change this. See genconfig --help for other details.