Thanks for sharing your project. It starting to make sense!
One of the reasons I couldn’t combine the two libraries into a single projucer is that my hacky attempts to make an android library were to take a working GUI application and change the application to a library, e.g.
apply plugin: 'com.android.library', and comment out
//applicationId "com.acme.myapp" while, in my host, setting the object to
com.roli.juce.JuceApp and calling the
OnCreate function on the
currentActivity of the host.
Now, when I change it to Dynamic Library in Projucer, the build doesn’t include
com.roli.juce.JuceApp, which obviously makes sense becaue its no longer a GUI App.
I tried then to create my own version of
com.acme.JuceApp (duplicating the code, with changes to package) – this works when my libray is hacked from the GUI App approach – but when I’m building a Dynamic Library this always results in assert error
I/JUCE: JUCE Assertion failure in juce_android_Threads.cpp:321 which comes from the
// You did not call Thread::initialiseJUCE which must be called at least once in your apk
// before using any JUCE APIs. The Projucer will automatically generate java code
// which will invoke Thread::initialiseJUCE for you.
Any ideas what am I missing in my Dynamic Library that would solve this?