[PR] Android Studio exporter additions

The Projucer
1

The following additions would make Projucer work much better for Android projects, without having to store build files in a VCS. It can be very frustrating to have Projucer destroy all your carefully adjusted build settings when saving, and have to redo them if they haven’t been saved in a VCS.

These are additions I am happy to make and send in a PR when I get the time, but it would be great if someone on the JUCE team could look into it too.

Projucer changes for Android Studio exporter:

  • Application class name, to fill in the manifest e.g.

    <application android:name=".MainApplication"  ...

  • Repositories (Project build.gradle)

  • Dependencies (app build.gradle).
    Default: compile "com.android.support:support-v4:+"

  • Separate compile, target and minSdk, e.g.:
    compileSdkVersion 23 minSdkVersion 10 targetSdkVersion 23

  • packagingOptions, e.g:

android.packagingOptions {
    exclude 'META-INF/ASL2.0'
    exclude 'META-INF/LICENSE'
    exclude 'META-INF/NOTICE'
}
  • settings.gradle additions, e.g.
include ':react-native-navigation'
project(':react-native-navigation').projectDir = new File(rootProject.projectDir, '../../node_modules/react-native-navigation/android/app/‘)
1 Like
2

Pull request complete: https://github.com/julianstorer/JUCE/pull/119
My full modification of JUCE for Android is now on the master branch of my JUCE fork https://github.com/adamski/JUCE

I will probably replace the packagingOptions with a ‘custom additions’ section.

3

@adamski hey I was wondering how can I build the Projucer from the sources on your branch? ie. how can I launch the Projucer with the additions you’ve built in?

4

You would clone or download the JUCE source code from my fork,


then find the relevant project in extras/Projucer/Builds to build the modified Projucer app for your development platform.