Repository navigation
Allow customizing JNI lib loading - #47
Merged
Merged
Conversation
wkornewald
changed the title
Owner
|
Please note that this lib is not tested with pdfium binaries other than bundled in this repo. |
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
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.
When building Flatpaks via Nucleus, the native libs are not part of the resources, but instead live pre-extracted in a libs/resources folder, so
System.loadLibrary()should be used directly. For even more flexibility this just allows fully customizing the loading process.This also needs to be combined with #46 for the best out of the box Nucleus Flatpak experience.