Split build process to also generate a static library#15
Conversation
|
There are a lot of changes and I'm not sure if I got the CMake code right. "It works on my device/project". 😆 |
|
Hi Christoph, I would like to follow your example to make the integration of LVGL more flexible, simpler, and streamlined. You wrote:
I'm going to start by trying this approach with hub75_lvgl to get some initial experience with it. Kind regards, P.S.: I have now integrated the latest hub75 driver into hub75_lvgl. hub75_lvgl_9_4_0_chained_2_cols_1_row.mp4Chained with settings CHAIN_COLS=2 and CHAIN_ROWS=1 hub75_lvgl_9_4_0_chained_1_col_2_rows.mp4Chained with settings CHAIN_COLS=1 and CHAIN_ROWS=2 |
To be used as a library within other CMake base projects, split the build into a static library and the demo application.
The hub75.hpp file is moved into a new
includedirectory to provide a defined public interface to library users.Where necessary, relative include paths including the
librarydirectory are changed just use the name of the file in question. The specific file will be found via the configured search path.With those changes, the library can be used within another project by specifying: