On Fri, Mar 6, 2026 at 10:55 AM Tomek CEDRO <[email protected]> wrote: > 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!
Sorry for the slight rant earlier. I normally say that when people are complaining that something is not working, it's mostly because they don't understand HOW it works. It stems from the frustration that you do A and expect B - actually C is happening. Of course you don't check if B actually happened, because in your mind that's obvious, and you continue to work on top of C... So this time I fell into this trap myself. Now that it's working (see https://github.com/apache/nuttx/pull/18517) I'm already a lot more positive about this KConfig option. :-) > 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. I'll stick to the tried & tested menuconfig for now. Already enough tools on my plate to manage. Cheers, Maarten
