Hi Alan,
On Sun, Nov 1, 2020, at 14:52, Alan Carvalho de Assis wrote:
> Since we will download the LVGL tarball with a Kconfig, we cannot
> display the menuconfig before it is downloaded and decompressed.
> And because its download depends on selected item on menuconfig we a
> classic dilemma here
Hi Matias,
The idea of using the Kconfig supplied by LVGL is to simplify our
building process, but of course, it needs to avoid some drawbacks that
can appear during this development.
Currently we already ship our own Kconfig
(apps/graphics/lvgl/Kconfig), but since LVGL is moving to Kconfig we
ne
I'd really hate to have to go through a separate configuration process. I would
think that we are losing functionality instead of gaining something in that
case. Also, if I understand correctly this would mean that we have one extra
config file to handle besides NuttX's one, and we have to keep
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
> 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 wi
