Closed napperley closed 2 years ago
Have you enabled EVDEV in lv_drv_conf.h
?
No I haven't. After I enabled EVDEV in the header file, rebuilt the LV Drivers library, and reran the linking task for the Kotlin Native program the linking error no longer occurs :). With the static library file I have noticed that there are significantly more symbols included, and the library file is now 2 MB in size instead of 22 KB.
You can enable/disable only what you really need. The disabled "modules" won't be built.
After the static library is generated for the LV Drivers library there is an error occurring during link time where the linker reported that the evdev_init symbol is missing.
There are some missing symbols in the static library. Here is the output after running
nm liblv_drivers.a
:Take note of the o files that are empty with no symbols (especially evdev.o and libinput.o). This is very strange to see with the static library file. Some o files are included that shouldn’t be present in the static library file (eg win32drv.o) when the Linux Frame Buffer backend is used. No o files in the static library file should be empty. Why are there missing symbols in the static library file?