-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build leads to shared library and standalone #127
Comments
FWIW, I am able to disable build of the standalones with |
when I made the repo split, I haven't taken into account also separated builds of the UI and library, just code separation, so I guess it's basically the same as the previous situation, including the static library.
I think we had some talk about it and both agree that needs to be changed in the Linux context, I see you are making 2 separated PKGBUILDs so I guess I should add some |
Making plugins depending on the shared library is not that simple as I thought so for the time being:
|
Hi! 👋
When building 1.2.3 for Arch Linux I noticed, that the build and install targets lead to the shared library and the standalones to be built and installed.
I get the following files after picking out the plugin related files:
I can of course remove those manually, but they should neither be built nor installed in this project.
Looking at what the created plugins link against, it appears those link against a static version of libsfizz.so.
Is this intended? Can this be changed?
The text was updated successfully, but these errors were encountered: