Do not install libbdarklycommon #166
Merged
Conversation
This file contains hidden or 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
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for #158
This includes a few changes to how libbdarklycommon is built and aligned with Breeze.
These changes were taken from https://invent.kde.org/plasma/breeze/-/commit/4a855ef3abacd6b7fede3773ce2e8b97393e5b53
The following shared object files will no longer be built.
/usr/lib64/libdarklycommon5.so.0
/usr/lib64/libdarklycommon6.so.0
It seems they are not required anymore, and it fixes the issue with Darkly not working properly on KDE Neon.