<div dir="ltr">Yes, I'm adding it to the apk, the problem is that if I set it like this:<div><br></div><div> #undef JDK_HOME<br> #define JDK_HOME "/lib/arm64/"<br></div><div><br></div><div>It needs to look at the root of JDK_HOME. I can't add folders.</div><div>And from the looks of the log it will look for it in /lib/arm64/jre/lib/aarch64/server/libjvm.so</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jan 23, 2021 at 5:33 PM Shaya Potter <<a href="mailto:spotter@gmail.com">spotter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>so seems related to the issue I mentioned<br><br></div><a href="https://stackoverflow.com/questions/59608865/library-is-not-accessible-for-the-namespace-classloader-namespace" target="_blank">https://stackoverflow.com/questions/59608865/library-is-not-accessible-for-the-namespace-classloader-namespace</a><br><br></div>seems to be that the solution is that you will have to include it in the apk itself.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jan 23, 2021 at 10:26 PM Vitor Dall'Acqua <<a href="mailto:veggav@gmail.com" target="_blank">veggav@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Well... managed to get it to see...</div><div><br></div><div>2021-01-23 18:21:35.375 T:19738 DEBUG <general>: CBlurayCallback::Logger - bdj.c:311: Opening /storage/emulated/0/JAVA/jre/lib/aarch64/server/libjvm ...<br> <br>2021-01-23 18:21:35.377 T:19738 DEBUG <general>: CBlurayCallback::Logger - dl_posix.c:54: can't open library '/storage/emulated/0/JAVA/jre/lib/aarch64/server/libjvm.so': dlopen failed: library "/storage/emulated/0/JAVA/jre/lib/aarch64/server/libjvm.so" needed or dlopened by "/mnt/expand/cab01563-bcca-48fa-a0bf-0fbddaf9b192/app/org.xbmc.kodi19DV-BHAaVSj7u8lhvDk_OSQttQ==/lib/arm64/libkodi.so" is not accessible for the namespace "classloader-namespace"<br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jan 23, 2021 at 3:30 PM Shaya Potter <<a href="mailto:spotter@gmail.com" target="_blank">spotter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><br>i looked at what they call "source code", its not source (unless I'm missing it). It's just the pre built binaries.<br><br></div>I didn't say that google did that exactly, I said, I think they have made it difficult to put executables there in Android Q (with that said, might not be a near term proble if the app isn't targeted specifically to android Q's API level, which kodi probably is not). What I also said, I dont know how that would impact dlopen (which is not directly executing the program) if android would block that as well.<br><br></div><div>with that said, I'd still think (perhaps incorrectly) from a security point of view, kodi would want to ship the jvm within their apk as this would prevent external things from breaking it and not have it provided by the user (then again, on all desktop environments it is provided by the user).<br></div><div dir="ltr"><br>for reference where I came across a discussion a bit ago: <a href="https://www.reddit.com/r/androiddev/comments/b2inbu/psa_android_q_blocks_executing_binaries_in_your/" target="_blank">https://www.reddit.com/r/androiddev/comments/b2inbu/psa_android_q_blocks_executing_binaries_in_your/</a><br><br></div><div>if I had to guess, it probably would work for now (even on Q), but in the future there might be issues as google prevents older and older api targets from being updated in the play store.<br></div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jan 23, 2021 at 8:08 PM Vitor Dall'Acqua <<a href="mailto:veggav@gmail.com" target="_blank">veggav@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">But Shaya, the source is present in the linked file here. <div><br></div><div>The thing is that it's beyond my capabilities try to add this to Kodi as a dependency. </div><div>Also another problem I'm seeing here is that while I'm able to pack into an apk the libjvm.so so it is installed when you install Kodi, this isn't the case for the .jar files. </div><div><br></div><div>You mentioned that Google made sure to close down the possibility of loading a .so file from outside the app folder?</div><div>So you think even if libbluray could read /storage/emulated/0/ it would fail in use the libjvm?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jan 23, 2021 at 2:30 PM Shaya Potter <<a href="mailto:spotter@gmail.com" target="_blank">spotter@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>vitor, I'd think that kodi's path manipulation wouldn't impact the jre at all. It's just for internal kodi use for themes and media and the like, but nothing to do with OS operations (and petri can verify if this or true, motivated the need for libbluray to have the ability to a pluggable set of file system operations that could be provided to it). But while libbluray can use the a provided set of operations, the jvm can't.<br></div><div><br></div><div>I'd think one of your goals should be to get the group that made those jvm binaries to release the source and build for it, then kodi can include it as part of their build process and even ship with it in the play store. I'd think vlc would be interested in this, as well? This would also be necessary as would have to ship different jvm's for 32 bit kodi and 64 bit.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jan 23, 2021 at 2:22 PM Vitor Dall'Acqua <<a href="mailto:veggav@gmail.com" target="_blank">veggav@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Petri, do you happen to have the source with your latest changes?<div><br></div><div><a href="http://code.videolan.org" target="_blank">code.videolan.org</a> is down and I would like to work on this during the weekend.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jan 22, 2021 at 6:08 PM Petri Hintukainen <<a href="mailto:phintuka@users.sourceforge.net" target="_blank">phintuka@users.sourceforge.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">pe, 2021-01-22 kello 16:54 -0300, Vitor Dall'Acqua kirjoitti:<br>
> I have not tried to build Java from source. <br>
> The version used by Termux, can be found as pre compiled and source<br>
> here:<br>
> <a href="https://github.com/Hax4us/java/releases/download/v8/jdk8_aarch64.tar.gz" rel="noreferrer" target="_blank">https://github.com/Hax4us/java/releases/download/v8/jdk8_aarch64.tar.gz</a><br>
> <br>
> I can give a go with Kodi, which is what I'm familiar with, to git<br>
> clone the latest changes from libbluray, add the lib/arm/client to it<br>
> and add the files from that archive linked here. <br>
> Does it still need a bin folder inside? is the structure correct<br>
> there?<br>
<br>
Structure seems to be normal. I think you need only files from<br>
/jdk8/jre/ and maybe from /glib/ (?).<br>
<br>
JAVA_HOME would point to .../jdk8/ or .../jdk8/jre/. Or, you could try<br>
if simply symlinking .../jdk8/jre/lib/aarch64/server/libjvm.so next to<br>
libbluray.so works.<br>
<br>
The files in top-level bin folder are wrapper scripts. Looking at<br>
those, you may need to set LD_LIBRARY_PATH so that libraries from /glib<br>
can be found. But I don't know if JVM needs those, or if those are only<br>
used with some of the applications.<br>
<br>
<br>
<br>
_______________________________________________<br>
libbluray-devel mailing list<br>
<a href="mailto:libbluray-devel@videolan.org" target="_blank">libbluray-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/libbluray-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/libbluray-devel</a><br>
</blockquote></div>
_______________________________________________<br>
libbluray-devel mailing list<br>
<a href="mailto:libbluray-devel@videolan.org" target="_blank">libbluray-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/libbluray-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/libbluray-devel</a><br>
</blockquote></div>
_______________________________________________<br>
libbluray-devel mailing list<br>
<a href="mailto:libbluray-devel@videolan.org" target="_blank">libbluray-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/libbluray-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/libbluray-devel</a><br>
</blockquote></div>
_______________________________________________<br>
libbluray-devel mailing list<br>
<a href="mailto:libbluray-devel@videolan.org" target="_blank">libbluray-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/libbluray-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/libbluray-devel</a><br>
</blockquote></div></div>
_______________________________________________<br>
libbluray-devel mailing list<br>
<a href="mailto:libbluray-devel@videolan.org" target="_blank">libbluray-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/libbluray-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/libbluray-devel</a><br>
</blockquote></div>
_______________________________________________<br>
libbluray-devel mailing list<br>
<a href="mailto:libbluray-devel@videolan.org" target="_blank">libbluray-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/libbluray-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/libbluray-devel</a><br>
</blockquote></div>
_______________________________________________<br>
libbluray-devel mailing list<br>
<a href="mailto:libbluray-devel@videolan.org" target="_blank">libbluray-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/libbluray-devel" rel="noreferrer" target="_blank">https://mailman.videolan.org/listinfo/libbluray-devel</a><br>
</blockquote></div>