Thanks Xavier: I looked inside the APK and confirmed the x86 .so is
in the libs/ folder. The java.lang.UnsatisfiedLinkError implys that
the app is attempting to load a native lib but the lib could not be
found. Is it possible that it found the lib but could not load it?
It detects the x86 native lib when building as described in #1
below. Why would that same lib work when adding it manually to an
app module? Loading manually is a workaround, but I would prefer
the ability to use the AAR bundle across all platforms. On 12/10/14, 3:26 PM, Xavier Ducrohet
wrote:
-- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
- AAR bundle support for x86 native libs Dan O'Neill
- Re: AAR bundle support for x86 native libs jdONeill gMail
- Re: AAR bundle support for x86 native libs Xavier Ducrohet
- Re: AAR bundle support for x86 native libs jdONeill gMail
- Re: AAR bundle support for x86 native libs jdONeill gMail
- Re: AAR bundle support for x86 native lib... Xavier Hallade
- Re: AAR bundle support for x86 nativ... jdONeill gMail
- Re: AAR bundle support for x86 n... Xavier Hallade
- Re: AAR bundle support for x... Dan O'Neill
- Re: AAR bundle support for x... Xavier Hallade
- Re: AAR bundle support for x... Dan O'Neill