Here’s how to make it work with Visual Studio, step by step:
Assumptions: you’ve got only c++ code in a project created in Visual Studio (VS2019 in my case, VS2017 gives the same project) basing on “Native-Activity application (Android)”. You haven’t changed AndroidManifest.xml nor build.xml (maybe only to get assets automatically).
I will be using MyGame in code etc
in packaging project (MyGame.Packaging) create “libs” folder. Add fmod.jar there. Open its properties and choose “Copy to output directory” to be “Copy always”.
in the same project create “src” folder. Add a new file in it, java code, MyGameActivity.java. Its content:
public class MyGameActivity extends android.app.NativeActivity
Go to its properties and set to always copy it (as in 1)
- Open AndroidManifest and set hasCode to true:
<application android:label="@string/app_name" android:hasCode="true">
and change android:name for activity to your class name (full path):
And that’s it.
You have to use mentioned folder names as build.xml relies on them. If you choose to use different names, you have to either modify build.xml (the original one in SDK folder) or provide dir variables. Assuming its you only java code, keep the names the way they are.
What should happen: build.xml will notice that hasCode is set to true, will then look for .java files in src folder and will compile them creating .class files. After that, it will get both .class file and fmod.jar (from libs folder) and turn it into classes.dex that will end up in apk.
Because android:name is changed and is based on android.app.NativeActivity two things happen:
- Both System.loadLibrary calls will get executed, this way fmod will be properly initialised and when calling “initialize” method you won’t get error and info in android log about missing call to JNI_OnLoad .
- Your app will run just as it was running before.
How to check if apk was prepared properly. Open apk file (change its extension to .zip and open is as zip) and unpack classes.dex. View it in any text viewer and look for “fmod” and “MyGame”. Both those phrases should be found.
It’s really easy but without any knowledge of how android stuff is built with build.xml you don’t know where to start (I did it the other way around, calling java from C++, then compiling java by hand, creating jars and trying to get them into apk, when I learned that build.xml can do all of that for me).