Maybe we keep a dummy Kconfig and override it during context? (thinking out loud...)
On Wed, Aug 26, 2020 at 3:49 PM Abdelatif Guettouche <abdelatif.guettou...@gmail.com> wrote: > > Generating the Kconfig file has to be done during preconfig otherwise > anything kconfig related won't work. We can't source a file that > doesn't exist yet. > As it is now LVGL is downloaded during context (the usual), I think > sourcing or just copying the Kconfig file from the LVGL folder would > cause the configuration phase to fail, specifically the call to make > olddefconfig. > > On Wed, Aug 26, 2020 at 2:37 PM Gregory Nutt <spudan...@gmail.com> wrote: > > > > > > >> If you can make LVGL optionally NOT generate its own config.h and > > >> .config we could indeed just include the Kconfig and Make.defs (as it is > > >> done now). > > > I think generating the config file would be part of a "toplevel" LVGL > > > build system which we would completely bypass. > > Couldn't it be done in the NuttX context target? The context target > > runs each time you build, but only does anything on the first build. > > There is the make target where are generated files and working > > directories are created. Could that target not also create the LVGL > > configuration then too? > >
