Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
647 views
in Technique[技术] by (71.8m points)

android - How can I specify per flavor buildType sourceSets?

I've got 2 flavors of an app that each have their own google maps (v1) key for debug and release (meaning 4 keys total). So I'd like to know if I can specify sourceSets based on the buildType and productFlavor. Essentially, I'm wondering how I can achieve something like this:

src
├── debug
│?? └── flavor1
│??     └── res
│           └── values
│               └── gmaps_key.xml
├── release
│   └──flavor1
│       └── res
│           └── values
│               └── gmaps_key.xml

Where gradle will use the src/<currentBuldType>/<currentProductFlavor>/* as part of its sourceSet.

Essentially I want it so that if I run gradle assembleFlavor1Debug it will include everything under src/main/*, src/flavor1/*, and src/debug/flavor1/*.

My build.gradle is super simple:

buildscript {
    repositories {
        mavenCentral()
    }   

    dependencies {
        classpath 'com.android.tools.build:gradle:0.5.0'
    }   
}

apply plugin: 'android'

android {
    compileSdkVersion 8

    productFlavors {
        flavor1 {
            packageName 'com.flavor1'
        }
        flavor2 {
            packageName 'com.flavor2'
        }
    }
}

Any thoughts? Or maybe a better approach to this?

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

I happened to come back to this because of a comment on my answer and realized that this answer is superfluous (still better than the accepted one which is even more so). For each productFlavor and buildType, combination and individual source sets already exist. i.e. src/{buildType}, src/{productFlavor} and src/{productFlavor}{buildType} are already available source folders.

So essentially, all that was needed for the OP was to put the resources in src/flavor1Debug which is equivalent to the src/debug/flavor1 that the OP envisions.

OLD ANSWER: I've done something similar with buildConfig but hopefully it should work with sourceSets.

Basically, you define the common stuff at the productFlavors level in a variable and keep adding things as you move down.

productFlavors {
        def common = 'src/main'

        flavor1 {
            def flavor = 'src/main/flavor1'
            buildTypes {
                debug {
                    sourceSets {
                        res.srcDirs = [ common + ',' + flavor + ',' + 'src/main/debug'
                    }
                }

                release {
                    sourceSets {
                        res.srcDirs = [ common + ',' + flavor + ',' + 'src/main/release'
                    }

            }
        }
}

I haven't tested this. I think you might need to use android.sourceSets instead of just sourceSets.

I've also needed to define separate resources for the productFlavors so I used a separate statement late in the build file. Like so:

android.sourceSets.flavor1 {
    res.srcDirs = ['flavor_resources/flavor1/res']
}

You should just be able to use android.sourceSets.flavor1.debug instead if you need to.

Also note that according to the Android Gradle user guide, using srcDir adds the directory to the default sources and srcDirs replaces them.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...