How to set variable according to gradle flavors

Question

I want to pass a variable test that I set differently per flavor as a define to the NDK. But for some reason he always passes the value of the last flavor.

Here is the build.gradle:

apply plugin: 'com.android.library'

def test

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.2"
    defaultPublishConfig "flavorARelease"
    publishNonDefault true

    defaultConfig {
        minSdkVersion 15
        targetSdkVersion 17

        ndk {
            moduleName "test"
            ldLibs "log"
        }
    }

    productFlavors {    
        flavorA {
            test = 1
        }

        flavorB {
            test = 2
        }    
    }

    buildTypes {    
        debug {
            ndk {
                if (cFlags == null) { cFlags = "" }
                cFlags = cFlags + " -DLOGGING=1 -DTEST="+test+" "
            }
            minifyEnabled false
        }
        release {
            ndk {
                if (cFlags == null) { cFlags = "" }
                cFlags = cFlags + " -DLOGGING=0 -DTEST="+test+" "
            }
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    compile fileTree(dir: 'libs', include: ['*.jar'])
    testCompile 'junit:junit:4.12'
    compile 'com.android.support:appcompat-v7:23.1.1'
}

And here are the CFLAG lines from the generated Android.mk

build/intermediates/ndk/flavorA/debug/Android.mk:

LOCAL_CFLAGS :=  -DLOGGING=1 -DTEST=2

I expected -DTEST=1 here

build/intermediates/ndk/flavorB/debug/Android.mk:

LOCAL_CFLAGS :=  -DLOGGING=1 -DTEST=2

So where is my mistake? Or how can I achieve my goal? Please also consider that the real problem is more complex and I want to make those defines in the "buildTypes" segment if possible.

score 26 · Answer 1 · answered Sep 19 '17 at 07:16

26

You can use buildConfigField

productFlavors {
    demo {
        buildConfigField "int", "FOO", "1"
        buildConfigField "String", "FOO_STRING", "\"foo1\""
    }
    full {
        buildConfigField "int", "FOO", "2"
        buildConfigField "String", "FOO_STRING", "\"foo2\""
    }
}

answered Sep 19 '17 at 07:16

Linh

57,942
23
262
279

6

And how would you access this from C in #ifdef? This only works for Java AFAIK. – Torge Sep 19 '17 at 11:18
How do you use this in Java? – sean Oct 20 '18 at 20:42
2

@sean Just call like `BuildConfig.FOO` or `BuildConfig.FOO_STRING` in Java. – iStar Apr 14 '19 at 07:09
How can you make different buildConfigField per flavor and also per buildType ? – ctorx May 16 '19 at 15:20

Torge · Accepted Answer · 2016-09-22T14:24:29.587

I found the solution:

First instead of def test specify a new field for all productFlavors

productFlavors.all {
    ext.dTest = null
}

Then this field is set in each flavor (code unchanged)

productFlavors {    
    flavorA {
        dTest = 1
    }

    flavorB {
        dTest = 2
    }    
}

And finally you can do this in the buildTypes

buildTypes {    
    all {
         productFlavors {
            all {
                ndk {
                    if (cFlags == null) { cFlags = "" }
                    cFlags = cFlags + " -DTEST="+dTest+" "
                }
            }
        }
    }
    debug {           
        minifyEnabled false
        ndk {
            if (cFlags == null) { cFlags = "" }
            cFlags = cFlags + " -DLOGGING=1 "
        }
    }
    release {
        minifyEnabled true
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

        ndk {
            if (cFlags == null) { cFlags = "" }
            cFlags = cFlags + " -DLOGGING=0 "
        }
    }
}

Here the full file:

apply plugin: 'com.android.library'

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.2"
    defaultPublishConfig "flavorARelease"
    publishNonDefault true

    defaultConfig {
        minSdkVersion 15
        targetSdkVersion 17

        ndk {
            moduleName "dTest"
            ldLibs "log"
        }
    }

    productFlavors.all {
        ext.dTest = null
    }

    productFlavors {    
        flavorA {
            dTest = 1
        }

        flavorB {
            dTest = 2
        }    
    }


    buildTypes {    
        all {
            productFlavors {
                all {
                    ndk {
                        if (cFlags == null) { cFlags = "" }
                        cFlags = cFlags + " -DTEST="+dTest+" "
                    }
                }
            }
        }
        debug {           
            minifyEnabled false
            ndk {
                if (cFlags == null) { cFlags = "" }
                cFlags = cFlags + " -DLOGGING=1 "
            }
        }
        release {
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

            ndk {
                if (cFlags == null) { cFlags = "" }
                cFlags = cFlags + " -DLOGGING=0 "
            }
        }
    }

}

**Test extends ConventionTask**. Therefore, your productFlavors wouldn't build since you are using a reserved keyword as variable. — IgorGanapolsky, Sep 20 '16 at 20:46
Am not sure if you refer to the question or the solution. In my real project it is not `test`, but a set of different variables. If this example is broken because of using `test` could you fix it? As I am really rusted with gradle again since I struggled with this problem way back. - Would changing all occurrences of `test` to `dTest` do the trick already? — Torge, Sep 21 '16 at 08:27
I was referring to the **productFlavors**, where you were declaring `Test`. I went ahead and renamed the variable. Thanks! — IgorGanapolsky, Sep 21 '16 at 13:51
i also need to achieve the same thing without ndk and dtest directly in debug and release respectively — Rockin, Jul 28 '19 at 22:26
cFlags is a NDK variable. Basically these are compiler flags for the C compiler. You can ignore the NDK stuff. should also work right in release/debug. the dTest extension variable is not part of the NDK in this example only used there. — Torge, Jul 29 '19 at 07:59

How to set variable according to gradle flavors

2 Answers2

Linked