How to refer to build variants in gradle experimental

[par...@gmail.com]

Gradle for library project compiles it using Release even though you are building the app in debug. 

So it ends up using NDEBUG even on the debug builds in the Library modules

More details on the bug 

There is a work around #60

dependencies {
    flavorDebugCompile project(path: ':custom_lib', configuration: "libraryDebug")
    flaveorReleaseCompile project(path: ':custom_lib', configuration: "libraryRelease")
}

more information http://stackoverflow.com/a/30134955

But in Experimental they have changed the syntax of gradle files, including creating flavours

when I try 

dependencies {
    flavorDebugCompile project([path: ':custom_lib', configuration: "libraryDebug"])

It gives the following error:

flavorDebugCompile method not found

[par...@gmail.com]

# the solution number should be #37, #60 is derivation of #37  

[Adrian Ivasku]

I use it like this, with experimental 0.4.0.

android.productFlavors {   
    create("arm") {
        ndk.abiFilters.add("armeabi")
    }
    create("arm7") {
        ndk.abiFilters.add("armeabi-v7a")
    }
    create("arm8") {
        ndk.abiFilters.add("arm64-v8a")
    }

    create("googleFree") {
        applicationId = "com.test.free"
    }

    create("googleFull") {
        applicationId = "com.test.full"       
    }

[Raymond Chiu]

Configuration dependencies do not work very well with the experimental plugin.  The workaround is to create the configuration first.  E.g.

configurations {
    flavorDebugCompile
}

[par...@gmail.com]

How would you call the configuration in Android Studio as an option in the Build Variant menu?

[Igor Ganapolsky]

Where exactly do you put this configurations { } block?

[Raymond Chiu]

In the build.gradle for the app,

Before setting the dependencies:

configurations {
    flavorDebugCompile

    flavorReleaseCompile
}

dependencies {
    flavorDebugCompile project(path: ':custom_lib', configuration: "libraryDebug")

    flavorReleaseCompile project(path: ':custom_lib', configuration: "libraryRelease")