EXTRA_ZEPHYR_MODULES causes lots of 'the choice symbol' warnings

[RobbieKhan]

Hello everyone.
I am working with freestanding app. In short structure of the project is as follows (example):

1. F:\Work\Zephyr\zephyrproject --- zephyr 4.1.0 west environment.
2. F:\Work\Zephyr\demo_project --- my freestanding app - not west environment, doesn't contain zephyr repo itself. It uses zephyr repo from the folder mentioned above!
   Work is done in VSCode with 'MCUXpresso for VS Code' - NXP IMXRT1176 is on board.

My project requires additional non-existing display driver. I have created new zephyr module with Kconfig and CMakeLists.txt - let's assume, that they are correct.
Now I want to link that module to my freestanding application.
In order to do so, I add following line to my app's main CMakeLists.txt before find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE}):
list(APPEND EXTRA_ZEPHYR_MODULES path_to_my_custom_module)

When I recompile (pristine) the project, I get tons of warnings from default Zephyr drivers, like:

... 100500+ more
[cmake] warning: the choice symbol WIFI_RANDOM_MAC_ADDRESS (defined at drivers/wifi/nrf_wifi/Kconfig.nrfwifi:536, drivers/wifi/nrf_wifi/Kconfig.nrfwifi:536) is defined with a prompt outside the choice
... 100500+ more
[cmake] warning: the choice symbol ISL29035_INTEGRATION_TIME_26 (defined at drivers/sensor/renesas/isl29035/Kconfig:50, drivers/sensor/renesas/isl29035/Kconfig:50) is defined with a prompt outside the choice
... 100500+ more

Compilation fails, because Zephyr treats that warnings as errors.
What am I doing wrong?
Why these warnings even appear? Zephyr starts to recompile the whole environment because new module was attached? Why default modules generate so many erroneous warnings?

Kind regards,
Robert

[DerekSnell]

Hi @RobbieKhan ,
I am no expert on these warnings. But searching the repo for a similar example, I found the handler_demo test appends an extra module similar to your app. Building this app for the mimxrt1170_evk@B//cm7 board with v4.1.0, I do see one Kconfig warning below. But not the long list like you reported.

Perhaps you can compare this test with your app and module? Best regards

warning: The choice symbol MCUBOOT_UTIL_LOG_LEVEL_WRN (defined at
subsys/logging/Kconfig.template.log_config:14) was selected (set =y), but no symbol ended up as the
choice selection. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MCUBOOT_UTIL_LOG_LEVEL_WRN and/or look up
MCUBOOT_UTIL_LOG_LEVEL_WRN in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

[RobbieKhan]

Hi, @DerekSnell.
Thank you for your tip! I started looking into it and finally found the issue.

I have created new zephyr module with Kconfig and CMakeLists.txt - let's assume, that they are correct.

That was actually a bad guess :)

The root of the problem was lying in my Kconfig files.
I was attaching source Kconfigs relatively to the module folder, like this:
source "drivers/Kconfig"
But I forgot, that source is expecting files relatively to the zephyr path. That's why it was sourcing Kconfig from F:/Work/Zephyr/zephyrproject/zephyr/drivers/Kconfig leading to duplicate inclusion of everything that is mentioned there and tons of that drivers related warnings.

Now I actually need to understand, how can I keep paths in Kconfig relative to my module folder :/