Incorporating the LVGL support into your application is straightforward. The essential starting point is to incorporate the LVGL eCos package (CYGPKG_LVGL) into your configuration.

This may be achieved directly using ecosconfig add on the command line, or the Build->Packages… menu item within the eCos Configuration Tool.

For the majority of situations the default LVGL configuration as defined in the package include/cyg/gfx/lv_conf.h header will suffice. Especially since only referenced code will be linked into the final application.

The package does provide some CDL configuration options that will affect the LVGL library construction.

If, however, greater control over the configuration of the LVGL library build is required then the developer can supply header files to #define or #undef options as desired to override the default settings. This is achieved by enabling the relevant configuration option, specifying a header file location, so that the build will include the referenced header.

The header file injection configuration option is:

If the requirement for a specific LVGL configuration update is part of another package (for example the platform (PLF) or variant (VAR). or some application library package) then this can easily be achieved in the package specific CDL by a simple requires statement. e.g.

    requires      { CYGBLD_LVGL_USER_CONFIG_HEADER == "<my_package/my_lvgl_config.h>" }
        

If using the ecosconfig tool to construct a build configuration, then a CDL fragmant can be imported to set the desired header file reference. e.g.

cat > my_lvgl.ecm <<EOF
cdl_option CYGBLD_LVGL_USER_CONFIG_HEADER {
    inferred_value 1 “my_lvgl_options.h”
}
EOF
ecosconfig import my_lvgl.ecm
        

Alternatively, for a specific build configuration .ecc file, the option can be manually set using the configtool GUI application with a suitable local or global path filename used to reference the required header for the build.