定义特定风味的buildconfigfield和buildType

Posted

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了定义特定风味的buildconfigfield和buildType相关的知识,希望对你有一定的参考价值。

我有2种口味,可以说香草和巧克力。我也有Debug和Release构建类型,我需要Vanilla Release的字段为true,而其他3个组合应该为false。

def BOOLEAN = "boolean"
def VARIABLE = "VARIABLE"
def TRUE = "true"
def FALSE = "false"

    VANILLA {

        debug {

            buildConfigField BOOLEAN, VARIABLE, FALSE

        }

        release {

            buildConfigField BOOLEAN, VARIABLE, TRUE

        }


    }

    CHOCOLATE {
        buildConfigField BOOLEAN, VARIABLE, FALSE
    }

我遇到错误,因此我猜想调试和发布技巧不起作用。可以这样做吗?

答案

查看变量并检查其名称:

productFlavors {
    vanilla {}
    chocolate {}
}

applicationVariants.all { variant ->
    println("Iterating variant: " + variant.getName())
    if (variant.getName() == "chocolateDebug") {
        variant.buildConfigField "boolean", "VARIABLE", "true"
    } else {
        variant.buildConfigField "boolean", "VARIABLE", "false"
    }
}
另一答案

[这是我在Simas answer下描述的一种不乏解决方案

buildTypes {
    debug {}
    release {}
}

productFlavors {
    vanilla {
        ext {
            variable = [debug: "vanilla-debug value", release: "vanilla-release value"]
        }
    }
    chocolate {
        ext {
            variable = [debug: "chocolate-debug value", release: "chocolate-release value"]
        }
    }
}

applicationVariants.all { variant ->
    def flavor = variant.productFlavors[0]
    variant.buildConfigField "boolean", "VARIABLE", ""${flavor.variable[variant.buildType.name]}""
}
另一答案

不幸的是,在Gradle构建系统中,buildTypesproductFlavors是两个单独的实体。

据我所知,要完成您想要实现的目标,您将需要创建另一种构建风格,例如:

buildTypes {
        debug{}
        release {}
    }

    productFlavors {
        vanillaDebug {
             buildConfigField BOOLEAN, VARIABLE, FALSE
        }
        vanillaRelease {
             buildConfigField BOOLEAN, VARIABLE, TRUE
        }
        chocolate {
             buildConfigField BOOLEAN, VARIABLE, FALSE
        }
    }
另一答案

这是我解决此问题的方法:

def GAME_DIMENSION = "game"
def BUILD_DIMENSION = "building"

flavorDimensions GAME_DIMENSION, BUILD_DIMENSION

productFlavors {
    lollipop {
        dimension BUILD_DIMENSION
        minSdkVersion 21
    }

    normal {
        dimension BUILD_DIMENSION
    }

    game_1 {
        dimension GAME_DIMENSION
        ext {
            fields = [
                    [type: 'String', name: 'TESTSTRING', values: [debug: 'debugstring', release: 'releasestring']],
                    [type: 'int', name: 'TESTINT', values: [debug: '1234', release: '31337']]
            ]
        }
    }

    game_2 {
        dimension GAME_DIMENSION
        ext {
            fields = []  // none for game_2
        }
    }
}

applicationVariants.all { variant ->

    // get the GAME dimension flavor
    def game = variant.getProductFlavors()
            .findAll({ flavor -> flavor.dimension == GAME_DIMENSION})
            .get(0)

    println "Adding " + game.ext.fields.size() + " custom buildConfigFields for flavor " + variant.name

    // loop over the fields and make appropriate buildConfigField
    game.ext.fields.each { field ->
        def fldType = field['type']
        def fldName = field['name']
        def fldValues = field['values']

        // get debug/release specific value from values array
        def fldSpecificValue = fldValues[variant.getBuildType().name]

        // add quotes for strings
        if (fldType == 'String') {
            fldSpecificValue = '"' + fldSpecificValue + '"'
        }

        println "    => " + fldType + " " + fldName + " = " + fldSpecificValue
        variant.buildConfigField fldType, fldName, fldSpecificValue
    }
}

((我尚无法确定ext.fields是否存在于调味剂中]

另一答案

对于您的特定情况,您也可以只使用defaultConfig播放:

defaultConfig {
    buildConfigField BOOLEAN, VARIABLE, TRUE
}

buildTypes {
    debug {
        buildConfigField BOOLEAN, VARIABLE, FALSE
    }
    release {
    }
}

productFlavors {
    VANILLA {
    }
    CHOCOLATE {
        buildConfigField BOOLEAN, VARIABLE, FALSE
    }
}

默认值为TRUE,但随后将FALSE应用于所有Debug版本和所有Chocolate版本。因此,唯一剩下的TRUE是VANILLA版本。

另一答案

您可以尝试多种口味的产品:

productFlavors {
        demo {
            applicationId "com.demo"
            versionCode 1
            versionName '1.0'
            ext {
                APP_BASE_URL = [debug: "${BASE_URL_DEV}", release: "${BASE_URL_PRODUCTION}"]
            }
        }
        demo1 {
            applicationId "com.demo1"
            versionCode 1
            versionName '1.2'
            ext {
                APP_BASE_URL = [debug: "${BASE_URL_DEV}", release: "${BASE_URL_PRODUCTION}"]
            }
        }


    applicationVariants.all { variant ->
            def flavor = variant.productFlavors[0]
            variant.buildConfigField "String", "BASE_URL", "${flavor.ext.APP_BASE_URL[variant.buildType.name]}"
        }
另一答案

@@ Simas Aswer是正确的,但在开关盒的情况下看起来会更好一些:

android {

    defaultConfig {
       ...
    }

    buildTypes {
        debug {
            ...
        }

        release {
            ...
        }

    }

    flavorDimensions "type"
    productFlavors {

        vanilla {
            dimension "type"
           ...
        }


        chocolate {
            dimension "type"
            ...
        }
    }

    applicationVariants.all { variant ->
        switch (variant.getName()) {
            case "vanillaDebug":
                variant.buildConfigField 'String', 'SDK_API_KEY', ""$vanillaSdkApiKeyDebug""
                break

            case "vanillaRelease":
                variant.buildConfigField 'String', 'SDK_API_KEY', ""$vanillaSdkApiKeyRelease""
                break

            case "chocolateDebug":
                variant.buildConfigField 'String', 'SDK_API_KEY', ""$chocolateSdkApiKeyDebug""
                break

            case "chocolateRelease":
                variant.buildConfigField 'String', 'SDK_API_KEY', ""$chocolateSdkApiKeyRelease""
                break

            default:
                throw new GradleException("The values are unknown for variant: ${variant.getName()}")
                break
        }
    }
}
另一答案
productFlavors {
    vanilla {}
    chocolate {}
}

buildTypes {
        release {
            productFlavors.vanilla {
                //your configuration for vanilla flavor with release buildType
            }
        }
        debug {
            productFlavors.chocolate{
                //your configuration for chocolate flavor with debug buildType
            }
        }
    }

以上是关于定义特定风味的buildconfigfield和buildType的主要内容,如果未能解决你的问题,请参考以下文章

特定风味+类型组合的清单

如何使用不同的资产来实现 Flutter 风味?

将风味图放在布局的ImageView中

想要在构建特定风味之前附加到我的build.gradle。这可能吗?

Android反射修改buildConfigField生成的属性失效问题

Android风味,Gradle sourceSets合并