> 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? On Sun, Nov 1, 2020 at 1:04 AM Brennan Ashton <bash...@brennanashton.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? > > Every other system I have used that does this has you supply the defconfig > to the top level build system. It you want to change settings you would do > make lvgl-menuconfig > make lvgl-savedefconfig > And the save the updated defconfig. > > So you might have > boards/sim/sim/config/LVGL/defconfig > boards/sim/sim/config/LVGL/lvgldefconfig > > The NuttX config would contain > LVGL_DEFCONFIG="boards/sim/sim/config/LVGL/lvgldefconfig" > > This is how you handle the Linux kernel or uboot in Buildroot. > > On Sat, Oct 31, 2020, 4:24 PM Matias N. <mat...@imap.cc> wrote: > > > But isn't the point that we would just source their Kconfig? > > What I mentioned previously is that maybe it can be done so that > > they can accept an external header providing the Kconfig defitions > > (in our case nuttx/config.h). > > > > Or maybe I'm missing something... > > > > On Sat, Oct 31, 2020, at 20:27, Abdelatif Guettouche wrote: > > > It's nice to revive this discussion. > > > > > > As I was saying in Github, I don't see a "not too awkward" way to > > > include the Kconfig file directly and use it as any Kconfig we have. > > > > > > BTW, is LVGL going to provide a script to convert the Kconfig to a > > > lv_config.h of some sort? If that's the case we'll only have to call > > > the script after we download the tarball. > > > > > > On Sat, Oct 31, 2020 at 4:38 PM Alan Carvalho de Assis > > > <acas...@gmail.com> wrote: > > > > > > > > Hi Everyone, > > > > > > > > The move to the Kconfig is finally happening and we would have the > > > > chance to make suggestions. > > > > > > > > Please take a look in the discussion here: > > > > > > > > https://github.com/lvgl/lvgl/pull/1875 > > > > > > > > Thank you Abdelatif for let me know about it, I didn't see the github > > > > notification. > > > > > > > > BR, > > > > > > > > Alan > > > > > > > > On 8/25/20, Alan Carvalho de Assis <acas...@gmail.com> wrote: > > > > > Hi Everyone, > > > > > > > > > > Mr. Gábor Kiss-Vámosi contacted and told me that LVGL is moving to > > use > > > > > Kconfig: > > > > > > > > > > "At LVGL we are planning to add a Kconfig file to the main repo but > > we > > > > > are not sure if it will harm the existing Kconfig based projects. > > > > > > > > > > Could you comment on what your requirements are and what we should > > > > > consider in order to allow NuttX to use LVGL's Kcofig file or - if > > > > > it's not possible - to make sure it won't bother your Kconfig file?" > > > > > > > > > > So, I think this is a good opportunity to make NuttX more integrated > > > > > with LVGL. Suggestions are welcome. > > > > > > > > > > Gábor, I added you CC here because I don't know if you are subscribed > > > > > to NuttX at Apache Foundation mailing list. > > > > > > > > > > BR, > > > > > > > > > > Alan > > > > > > > > > >
