Closed lbuque closed 1 year ago
Why don't you fork and use lv_micropython?
lv_micropython is Micropython fork where LVGL integration is already done.
lv_micropython modifies micropython on the build system, which will make micropython update, and lv_micropython cannot adapt to the latest version of micropython very quickly. And I think, lv_binding_micropython should be an independent module, it should work with micropython very quickly. Rather than being highly integrated with lv_micropython.
And I think, lv_binding_micropython should be an independent module, it should work with micropython very quickly. Rather than being highly integrated with lv_micropython.
Unfortunately, today lv_binding_micropython is not a Micropython independent module since it requires some changes in Micropython itself to work. For example, it uses Micropython's GC for LVGL memory allocations.
If you don't want to use lv_micropython directly, you can diff lv_micropython vs. upstream Micropython, see the changes and adapt them on your Micropython fork.
Here is a list of steps for integrating lv_binding_micropython in your Micropython fork (a little outdated): https://github.com/lvgl/lv_binding_micropython#adding-micropython-bindings-to-a-project
I want to integrate lvgl on micropython, but it compiles wrongly, what should I do?
port: esp32 micropython: micropython/micropython v1.19.1