runtime.loadlibrary("libOpencl.so") from ndk by purego

[Matej Magat]

well I know that android is specific platform, but I fork and improve wrapper of OpenCL, in termux when I set  `LD_LIBRARY_PATH=/system/vendor/lib64:$LD_LIBRARY_PATH` it is work, so my question  is there option call by jni runtime.loadlibrary("libOpencl.so") and after that call C.dlopen() (purego can do that without cgo), or this is ultimate restrictions?

[enh]

well, OpenCL isn't part of _Android_ so whether there will be a library at all will depend on the specific device, and whether that library is accessible by apps will depend on the specific device. if your app needs to run on multiple devices, you'll have to have a non-OpenCL path anyway. if your app is going to be built in to a specific device, you can probably get the folks who own the OpenCL implementation on that device to make sure it's accessible to your app.

On Mon, Mar 18, 2024 at 6:22 PM Matej Magat <matej...@gmail.com> wrote:

well I know that android is specific platform, but I fork and improve wrapper of OpenCL, in termux when I set  `LD_LIBRARY_PATH=/system/vendor/lib64:$LD_LIBRARY_PATH` it is work, so my question  is there option call by jni runtime.loadlibrary("libOpencl.so") and after that call C.dlopen() (purego can do that without cgo), or this is ultimate restrictions?

--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-ndk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/089d3f06-3f01-418f-96e9-0305dd02bff4n%40googlegroups.com.