You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
The file lv_rnd_unicodes.h incorrectly uses a relative path to include the lvgl.h header file. The current include statement #include "../lvgl.h" fails because lvgl.h is not located in the specified path. This could lead to compilation errors when the header is included in projects.
How to reproduce?
Steps to Reproduce:
Set up a project including the LVGL library.
Attempt to include lv_rnd_unicodes.h in any source file.
Compile the project.
Observe the compilation error related to the missing lvgl.h file.
Proposed Fix:
Change the include statement from:
#include "../lvgl.h"
to an absolute path based on the typical project structure:
#include "lvgl/lvgl.h"
Impact:
This change would prevent compilation errors and improve the usability of the library in diverse project setups.
The text was updated successfully, but these errors were encountered:
kisvegabor
added a commit
to kisvegabor/lvgl_upstream
that referenced
this issue
Apr 28, 2024
LVGL version
v9.1
What happened?
Environment:
Operating System: Linux
Library Version: V9.1
Description:
The file
lv_rnd_unicodes.h
incorrectly uses a relative path to include thelvgl.h
header file. The current include statement #include "../lvgl.h
" fails becauselvgl.h
is not located in the specified path. This could lead to compilation errors when the header is included in projects.How to reproduce?
Steps to Reproduce:
Set up a project including the LVGL library.
Attempt to include
lv_rnd_unicodes.h
in any source file.Compile the project.
Observe the compilation error related to the missing
lvgl.h
file.Proposed Fix:
Change the include statement from:
#include "../lvgl.h"
to an absolute path based on the typical project structure:
#include "lvgl/lvgl.h"
Impact:
This change would prevent compilation errors and improve the usability of the library in diverse project setups.
The text was updated successfully, but these errors were encountered: