Closed MohitMaliFtechiz closed 1 year ago
Patch and project coverage have no change.
Comparison is base (
ab7bbc1
) 92.65% compared to head (eaa957f
) 92.65%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
I wonder if we could have a static block to initialize this. This way you wouldn't have to call JNIKiwix()
at all.
I wonder if we could have a static block to initialize this. This way you wouldn't have to call JNIKiwix() at all.
We can directly load these .so
files into Android code as mentioned below
For making the static block:
Relinker needs the Android context to load the .so
files, so we need to provide the context to it, for this reason, it has done this way.
As we can do this on the Android side, we can manage the loading of the bindings on the Android side.
Relinker needs the Android context to load the .so files, so we need to provide the context to it, for this reason, it has done this way.
Indeed.
As we can do this on the Android side, we can manage the loading of the bindings on the Android side.
Are you saying that we should remove JNIKiwix
function from the wrapper ? You will doing it on caller (android, test) side ?
Are you saying that we should remove JNIKiwix function from the wrapper ? You will doing it on caller (android, test) side ?
@mgautierfr, Yes we can directly load the .so
files of libkiwix in Android code with relinker
as mentioned in the above screenshot.
Sorry for jumping here, but this is the role of the library to handle all these .so details. Library should just work when imported in kiwix-android.
Fixes #39