New Tutorial: Using SWIG instead of JNI on Android

edited February 2016 in General discussions
Hi everyone!

I've just written a tutorial about using SWIG to access platform functionality on Android. The method described in the tutorial is an alternative to using JNI directly, so that SWIG does the dirty work. You can use this method to access anything you'd only be able to access from Java on Android. The tutorial exposes the vibration function, but many things require this, such as Ad integration, in-app purchases, "Share on Facebook" etc :)

Here's the tutorial: I hope it'll be helpful for someone.

In my own project, I've taken this one step further, and completely automated the process, so that whenever I need to expose any new functionality, I just do it in Java, and I get it immediately on the Orx side, so it's as easy as working natively with the Android SDK. I didn't describe this in the tutorial though, as it's very specific to my project setup. If there's interest I can also write a follow-up tutorial explaining that.



Sign In or Register to comment.