Why does ndk/jni building no longer work in 1.8.2?

You must Login before you can answer or comment on any questions.

I don't know what version it stopped working on; I'm developing a new module in 1.8.2. Files placed in the JNI directory do not get built as described in http://developer.appcelerator.com/blog/2011/01/titanium-and-the-android-ndk.html.

I am still testing, but it appears that I can fix it by adding the following code to module/android/build.xml:

<exec executable="${ndk.build}" dir="${jni}">
    <arg line="V=0" />
</exec>
Why was this support removed? Was that intentional? Will it be coming back? I'd rather not have to patch all sdk versions just to use ndk in my module...

Or is there a new method that I haven't found? Perhaps I overlooked something?

— asked 1 year ago by Richard Bateman
4 Comments
  • And naturally adding that line to the build.xml breaks it when there isn't a JNI folder, so I need to find a more elegant solution (which is probably easy, but I'm not a java guy =])

    — commented 1 year ago by Richard Bateman

  • For others with this problem, we have updated the build.xml file with this one: https://gist.github.com/8a8970fbe10e1de22fde and it works both with and without a jni dir

    — commented 1 year ago by Richard Bateman

  • Aparently the appcelerator guys don't bother reading these, since I still haven't seen a response. 2.0.1.GA2 is out and has the same issue. It's a simple fix; perhaps I'll try submitting a pull request, since nothing else seems to be getting anyone's attention. https://gist.github.com/ff6cf3b8100bbaf383fb contains two files, one for 1.8.2 and one for 2.0.1.GA2

    — commented 1 year ago by Richard Bateman

  • Show 1 more comment

1 Answer

Your Answer

Think you can help? Login to answer this question!