-
Notifications
You must be signed in to change notification settings - Fork 171
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
build: Build and install static library
This is useful for client applications. More cleanup may be done afterwards. Relate-to: lvgl/lvgl#2534 Relate-to: https://git.ostc-eu.org/OSTC/planning/core-os/-/issues/219 Forwarded: #10 Signed-off-by: Philippe Coval <[email protected]>
- Loading branch information
Showing
1 changed file
with
38 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5d5b30e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I started this project to simulate my embedded development. This would be with the library compiled directly into the executable. By changing what is built and how I'm worried we are diverging too far away from that original goal?
5d5b30e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yea I know it's not perfect but I reused your WIP branch, to build an other app using SDL2 it worked for me
https://git.ostc-eu.org/rzr/dialog-lvgl
https://forum.lvgl.io/c/my-projects/10
yes but this be can cleaned up but I won't cause any harm
5d5b30e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I right in saying that the default build is now a linked library rather than a single executable? My slight issue with this is that this may work for you, but does it break anything for the other users of this project? I know I enjoy having a single executable that I can easily share with others.
If the default was to build the project as a single executable, but the Makefile could be switched over to create a library and executable that would be better.
Apologies if I've misunderstood the changes to the Makefile.
5d5b30e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
default will build the executable linked to static lib (which contain the demo app too) this is the same lib I reused for an other app.
It worked enough to support by yocto system ( lvgl/lvgl#2534 )
I am currently trying to rebuild latest lvgl
5d5b30e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the part I have a problem with. I realise doing this suits your needs, but selfishly, they don't suit mine. If the pull request left the original build process in place, but could be configured to the new build process I would be willing to consider it.