- appcompat library
- android-volley library
- jni folder
- Core jni folder (C++ files called from Java code)
- Sym-linked Application.mk
- Sym-linked directories to additional C++ code
Ideally I'd like to import everything into Android Studio as one project/workspace (not sure of the terminology), but it seems I only get the Eclipse-to-Gradle importer if I pick ONE of the six app projects. Even so, when I pick one of them, the importer fails because (I think) it can't figure out the JNI setup. After clicking through the import wizard, Android Studio freezes for a while and then eventually unfreezes and remains on the Welcome window. I then click "Open Project" and try to open the project it just created, but the IDE has a "FileNotFoundException" and lists one of the sym-linked files from the JNI directory. None of my code shows up in the Project window in Android Studio, and I get a message about "Unlinked Gradle project?" but the "Import Gradle Project" dialog fails with the message "Build script error; unsupported Gradle DSL method found: 'release()'"
Several Android Studio releases ago, I tried this and it worked much better (the import-summary.txt file said it skipped most of the jni stuff, but at least it somewhat worked). Is this a regression or just not implemented yet? Any advice?