On Sun, Nov 1, 2020, 2:24 AM Abdelatif Guettouche < abdelatif.guettou...@gmail.com> wrote:
> > I'm confused how this would work. Don't you need to download the source > > tarball which is controlled via kconfig before you could source it? > > This is the part I'm calling "awkward", we can provide a dummy Kconfig > that we override when we download the tarall (during context target). > However we will not have the LVGL Kconfig options until that happens. > (which is precisely the awkward part.) > > > It you want to change settings you would do > > make lvgl-menuconfig > > make lvgl-savedefconfig > > Who will provide these targets? > We would provide them. They would also trigger downloading and exactracting the tarball. Then we would be calling make menuconfig etc... against the LVGL project. For an example of what I am talking about see section 7 here https://buildroot.org/downloads/manual/manual.html#_configuration_of_other_components And also section 9.1 for how the defconfigs are stored for these components. --Brennan
