-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google pixel support #49
Comments
I'm lacking some context here, and don't even know what the target architecture of the Google pixel is. |
`libOpenCL-pixel.so is Google pixel's openCL lib name (like libPVROCL) for powerVR. Its android with mostly arm64-v8 arch. I can open a pull request once this works. |
That word "mostly" is one point raises the question for me here. The native library that is supposed to be loaded has to match the architecture. And this information has to be encoded in the name of the library. So there is a function in the
or
I assume that there is no difference between Another question that is relevant here: Is there a difference between "Android on Google Pixel" and "Android elsewhere"? The point is: If we add a single
? If it has to be linked against different
That sounds like a bit of pain in the back, but ... well, whatever Google is doing there, it could be manageable. The question is: Can we unambiguously identify the "Pixel" case in JOCL/src/main/java/org/jocl/LibUtils.java Line 546 in fefa66d
|
Thanks for the amazing library. work flawlessly on desktop and android phones.
But this is not able to work on google pixel phones, these pixels have libOpenCL-pixel.so that needs to be loaded.
tnn also had some problems with pixel and this could be a reference issue for how to fix this issue
Tencent/TNN#398
The text was updated successfully, but these errors were encountered: