If there were a Kconfig in the top-level LVGL directory, then the apps/lvgl/Kconfig could simply "source lvgl/Kconfig". I don't believe that introduces any new, serious coupling between apps and LVGL. There are already expectations of what will be available in LVGL source trees. Adding the expectation of a Kconfig file would be the only addition.Of course it would be cool if you could simply do "make menuconfig" on NuttX and have LVGL options appear there, but I believe that would couple LVGL and NuttX build systems which may not be the best idea. I'm not sure if that can be done cleanly (it would always produce one .config and config.h which both would have to read).
- LVGL moving to Kconfig, how we could integrated bet... Alan Carvalho de Assis
- Re: LVGL moving to Kconfig, how we could integ... Matias N.
- Re: LVGL moving to Kconfig, how we could i... Gregory Nutt
- Re: LVGL moving to Kconfig, how we could i... Gábor Kiss-Vámosi
- Re: LVGL moving to Kconfig, how we cou... Matias N.
- Re: LVGL moving to Kconfig, how we... Abdelatif Guettouche
- Re: LVGL moving to Kconfig, h... Gregory Nutt
- Re: LVGL moving to Kconfi... Abdelatif Guettouche
- Re: LVGL moving to Kc... Abdelatif Guettouche
- Re: LVGL moving to Kc... Brennan Ashton
- Re: LVGL moving to Kconfig, how we... Gábor Kiss-Vámosi
- Re: LVGL moving to Kconfig, how we could integ... Gábor Kiss-Vámosi
- Re: LVGL moving to Kconfig, how we could integ... Alan Carvalho de Assis