embeddedt

I am not a lawyer, so this is just my understanding of the situation. The way EPDiy is included in the source tree is a separate topic from the question...

LGPL improves the situation but still requires some sort of dynamic linking on the target platform, or the ability for a user of the product to rebuild the firmware with...

The question of linking/licensing still needs to be resolved. From my perspective, we can't include LGPL code in this repository without some sort of prominent disclaimer, since dynamic linking isn't...

It sounds like you are using v8; I am not sure that this repo has been updated to that version yet.

@petestewardson-schneider https://github.com/lvgl/lv_port_esp32/blob/c1f43bfb090df293059ab52baabbdbdd8df00712/components/lv_examples/lv_ex_conf.h#L45

I apologize for my forgetfulness, but the long-term plan is to eventually merge this and `lv_drivers` together, right?

`touch_driver_read` needs to be updated to v8, otherwise, I'm pretty sure LVGL will just hang when it tries to read from the touchscreen. That update is being worked on in...

I would suggest not using Kconfig for this. Kconfig is not a very dynamic configuration language. While it does support hiding/showing options based on dependencies, the options all have to...

If you can give me a sequence of commands to run with a fresh copy of ESP-IDF, I'd be happy to try and configure the GitHub action for you.

I think so, since `menuconfig` wouldn't be available at CI time.