According to this rule, adle snippet above will also generate an assembleJnidebug task, and assemble would be made to depend on it the same way it depends on the assembleDebug and assembleRelease tasks. When the debug and release Build Types are pre-created, their tasks are automatically created as well. The assembleDebug and assembleRelease tasks have already been mentioned, and this is where they come from. This means the Build Type names cannot be main or androidTest (this is enforced by the plugin), and that they have to be unique.Īdditionally, for each Build Type, a new assemble task is created, e.g.

src/debug/java directory can be used to add sources that will only be compiled for the debug APK. In addition to modifying build properties, Build Types can be used to add specific code and resources. For each Build Type, a new matching sourceSet is created, with a default location of src//, e.g. See the DSL Reference for a list of all properties that can be configured on a build type.

Keep configuring the jnidebug, by enabling debug build of the JNI component, and add a different package suffix.Ĭreating new Build Types is as easy as using a new element under the buildTypes container, either to call initWith() or to configure it with a closure.

Creates a new BuildType called jnidebug and configure it to be a copy of the debug build type.

debug to be able to install both debug and release apk on the same device

Configures the default debug Build Type:.

The above snippet achieves the following:

5.2 Build Type + Product Flavor = Build Variant.

4.3 Resolving conflicts between main and test APK.

3.3.2 Differences between a Project and a Library Project.

3 Dependencies, Android Libraries and Multi-project setup.

Dendroid setup android studio gradle