On Fri, Mar 6, 2026 at 10:35 AM Maarten Zanders <[email protected]> wrote: > (..) > But the nastiest thing IMHO is the behavior of DEFAULT_SMALL itself. > It 'works' when starting from a defconfig. But toggling it in > menuconfig has different behavior due to how it's used in other > configuration items. I'll be taking a wide curve around it in the > future...
This comes from Kconfig architecture. We know about this problem, but no good solution, this also annoys me to enable all needed stuff by hand by cycling over all dependencies :\ Long story short: 1. "select" will select what is necessary but then you end up in most thing enabled even those you don't need. 2. "depends on" is safer but requires you to take some time to enable all dependencies by hand. 3. There is a mix of both that may cause behavior you describe. You may want to use kconfig-tweak to just select specific option in one terminal and watch the dependencies in second terminal over kconfig menu. Yes this is PITA but there are too many options for too many architectures and peripherals and modules. Once set the problem is gone :-P All big projects using Kconfig have this problem. If you know any better solution please let us know! Another idea here - if you use kconfig-frontends package you may also try kconfig python module from Espressif which is more up to date and may provide better functionalities here? I use that older frontends version. -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
