My prj.conf was growing quite large so I split it into several `prj-<section>.conf files for sections that I wasn't working on and moved them to a "config" subdirectory
Example: `config/prj-zephyr.conf`
# Logging (Core) CONFIG_LOG=y CONFIG_LOG_MODE_DEFERRED=y CONFIG_LOG_BUFFER_SIZE=16384 CONFIG_LOG_BACKEND_UART=y # Log through UART0 CONFIG_LOG_BACKEND_RTT=n # Shell disabled because it interferes with logging CONFIG_SHELL=n CONFIG_MAIN_STACK_SIZE=4096 # Some command handlers require a large stack. CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
Fragments are added to the build using the "Kconfig fragments" list in the VSCode build configuration (OVERLAY_CONFIG on command line) and are listed under "input files" in the editor
However the Kconfig extension shows "no context" when I open any of these fragment files and prj.conf shows warnings whenever I set an option there that depends on the fragments (e.g. attempting to over-ride a log level). The latter may actually be intended as it seems fragments are added after prj.conf based on the .config output
What I would like to see here is fragments being supported in editor (because a multi-page conf file is a PITA to use) and also a way to add fragments before prj.conf (so prj.conf can over-write). I believe based on the docs the Zephyr CONF_FILE variable accepts a list of files so maybe the editor could support that and order could be managed that way?
