[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Android support
- From: Marc Balmer <marc@...>
- Date: Mon, 26 Dec 2016 11:34:31 +0100
So I just read your slides, quite depressing to hear that Google puts so
little effort into the NDK.
For the record, there is actually a Java function you can use to query
the System.loadLibrary() path, but for now I go with hardcoding
/data/data/packagename/lib. Works for me so far.
It's in the preceding slide (33?). However, I forgot to say that you
should never actually rely on that path. That is a private
implementation detail and Google has refused to give us a public API
for the path. Google is also pretty flippant about breaking
existing/shipping binaries already on the store for those who use the
NDK. For example, I've heard a surprising number of people were broken
by the recent changes in the rules for SONAME.
Thanks for your help!