I am still working on creating an android shared library with juce code inside. No problems creating it, but when I create a threadpool object inside a library, I get a segmentation fault. I can create a threadpool inside an application, but just not from within a library. Do you know of any obvious reason why this won't work?
I cannot step into the library code from within the android debugger. But I've narrowed it down by creating a shared library that does only that: constructing a threadpool object. This is the stack I get at that point:
Thread  (Suspended: Signal 'SIGSEGV' received. Description: Segmentation fault.)
8 _JavaVM::AttachCurrentThread() 0x751c00dc
7 juce::ThreadLocalJNIEnvHolder::attachToCurrentThread() 0x752279d4
6 juce::ThreadLocalJNIEnvHolder::attach() 0x752275dc
5 <symbol is not available> 0x7522ad28
4 threadEntryProc() 0x7522ad94
3 __thread_entry() 0x4006d174
2 pthread_create() 0x4006d30c
1 <symbol is not available> 0x00000000
While i don't know the ins and outs of it, it look like some JNI code is called here. Does that mean that the compiler instructions (JUCE_ANDROID_ACTIVITY_CLASSNAME and JUCE_ANDROID_ACTIVITY_CLASSPATH) are used here?