JavaCPP and Proguard issue
4 名作者發佈了 17 個帖子
|
|
IplImage.create(400, 400, IPL_DEPTH_8U, 4)
|
On 12/01/2013 10:50 PM, Michael David Pedersen wrote:
> I'm running out of ideas for this one, so any help would be greatly appreciated.
>
> By the way, I noticed an issue that might be related:
>
> https://code.google.com/p/
>
> But I don't think this is the source of my problem.
error message than NullPointerException.
So, can you try the latest updates from the source repository:
https://javacpp.googlecode.
And post the error message that you get with that one? Thanks!
Samuel
|
|
|
|
|
We don't need the NDK to build JavaCPP, just the JDK.
--- 顯示引用文字 -
You received this message because you are subscribed to the Google Groups "javacpp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to javacpp-proje...@googlegroups.com .
For more options, visit https://groups.google.com/groups/opt_out .
|
So, can you check what errors you get with ProGuard that you do not get without? Thanks!
--Just an update that I think the issue may arise from getResourceAsStream failing. I've adapted my proguard-project file to keep resource directories, and it does indeed look like the javacp/properties directory and files are preserved in the APK. Unfortunately this hasn't solved the problem.
Michael
You received this message because you are subscribed to the Google Groups "javacpp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to javacpp-proje...@googlegroups.com .
For more options, visit https://groups.google.com/groups/opt_out .
|
|
On 12/02/2013 05:00 PM, Michael David Pedersen wrote:
> Hi Samuel,
>
> Thank you again for your reply.
>
> I think you may have missed my last two messages listing the error
> output. I summarise below the errors I get after using Proguard:
the same error messages without ProGuard. These messages do not look
like fatal error messages. We're not supposed to have libraries named
"jniPointer" or "gnustl_static" anyway, so my guess was these errors
showed up in any case, but you're saying they don't and they only happen
with ProGuard??
Samuel
|
I got the messages, thanks, but I was under the impression that you get
the same error messages without ProGuard. These messages do not look
like fatal error messages. We're not supposed to have libraries named
"jniPointer" or "gnustl_static" anyway, so my guess was these errors
showed up in any case, but you're saying they don't and they only happen
with ProGuard??
|
On 12/02/2013 05:52 PM, Michael David Pedersen wrote:
> These errors only show up when using Proguard, and the
> UnsatisfiedLinkExceptions are indeed fatal.
>
> I've confirmed that getResourcesAsStream appears to return correctly, so
> that wasn't the issue. I'll continue debugging tonight.
http://proguard.sourceforge.
That's ok for most annotations as they are not required at runtime,
except for the @Platform one on the top class, because that's where the
library name is provided. However, if we use System.loadLibrary() to
load the libraries instead of Loader.load(), then we don't need to worry
about even that annotation...
Samuel
|
http://code.google.com/p/
Let me know if that works, thanks!
Samuel
|
|
|
|
Hi Michael and Samuel,
I am facing the same problems as described in this thread. JavaCPP and JavaCV along with Ffmpeg libraries work fine without proguard but when using Proguard, I get the errors above. Unfortunately upgrading to Proguard 4.11 and using -keepattributes *Annotation* do not work for me.
Do you mind sharing how you solved the problem? Can you post your Proguard.cfg file please?
Thanks,Jinesh