blocks|key|74805|text|在Gradle的配置阶段，我找不到一种干净的方法来获取当前的构建类型。相反，我为每个构建类型分别定义了依赖关系，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|74806|debugCompile+project(path:+':lib1',+configuration:+'debug')
releaseCompile+project(path:+':lib1',+configuration:+'release')|code-block|syntax|javascript|74807|如果您有许多构建类型和许多项目依赖项，这可能会变得非常冗长，但可以添加一个函数来使依赖项成为一行程序。您需要将以下代码添加到主Gradle构建文件中：|74808|subprojects+{
++++android+{
++++++++dependencies.metaClass.allCompile+{+dependency+->
++++++++++++buildTypes.each+{+buildType+->
++++++++++++++++"${buildType.name}Compile"+project(path:+":${dependency.name}",+configuration:+buildType.name)
++++++++++++}
++++++++}
++++}
}|74809|然后您可以在Gradle模块中添加项目依赖项，如下所示：|74810|allCompile+project(':lib1')|74811|如果您还使用构建风格，则必须调整解决方案。有关该功能的文档，请参阅此链接：http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Library-Publication|offset|length|74812|请注意，安卓团队正在对这种行为进行改进：https://code.google.com/p/android/issues/detail?id=52962|74813|entityMap|0|LINK|mutability|MUTABLE|url|http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Library-Publication|1|https://code.google.com/p/android/issues/detail?id=52962^0|0|0|0|0|0|0|11|2E|0|0|K|1K|1|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1A|8|@]|9|@$Q|1B|R|1C|1|1D]]|A|$]]|$1|S|3|T|5|6|7|1E|8|@]|9|@$Q|1F|R|1G|1|1H]]|A|$]]|$1|U|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|13]]]]

I could not find a clean way to get the current build type during the configuration phase of Gradle. Instead I define the dependency for each build type separately like that:

<pre><code>debugCompile project(path: ':lib1', configuration: 'debug')
releaseCompile project(path: ':lib1', configuration: 'release')
</code></pre>

If you have many build types and many project dependencies this can get very verbose, but it is possible to add a function to make the dependency a one-liner. You need to add this to your main Gradle build file:

<pre><code>subprojects {
 android {
 dependencies.metaClass.allCompile { dependency -&gt;
 buildTypes.each { buildType -&gt;
 "${buildType.name}Compile" project(path: ":${dependency.name}", configuration: buildType.name)
 }
 }
 }
}
</code></pre>

Then you can add project dependencies in your Gradle modules like this:

<pre><code>allCompile project(':lib1')
</code></pre>

If you also use build flavors you would have to adapt the solution. See this link for a documentation of the feature:
<a href="http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Library-Publication" rel="noreferrer">http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Library-Publication</a>

Please note that the Android team is working on an improvement for this behaviour:
<a href="https://code.google.com/p/android/issues/detail?id=52962" rel="noreferrer">https://code.google.com/p/android/issues/detail?id=52962</a>

blocks|key|74849|text|添加一个任务，该任务依赖于调用后的每个assembleXxx任务和属性设置|type|unstyled|depth|inlineStyleRanges|entityRanges|data|74850|ext+{
++++currentConfig+=+""
}
task+generateConfigProperty(dependsOn:+'installDebug')+{

++++android.applicationVariants.all+{+variant+->
++++++++variant.outputs.each+{+output+->

++++++++++++def+taskName+=+"taskindicate$output.name"
++++++++++++task+"$taskName"()+<<+{
++++++++++++++++project.ext.set("currentConfig",+"$output.name")
++++++++++++}
++++++++++++output.assemble.dependsOn+"taskindicate$output.name"
++++++++}
++++}

}

task+getConfig(dependsOn:+['installDebug',+'generateConfigProperty'])+<<+{
++++println("My+config+is+$currentConfig")
}|code-block|syntax|javascript|74851|取自answer的想法|offset|length|74852|entityMap|0|LINK|mutability|MUTABLE|url|https://groups.google.com/d/msg/adt-dev/iSZuHNSdJHI/R8ZYF9486ecJ^0|0|0|2|6|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Add a task which depends on each assembleXxx task and property setting up after it invoked

<pre><code>ext {
 currentConfig = ""
}
task generateConfigProperty(dependsOn: 'installDebug') {

 android.applicationVariants.all { variant -&gt;
 variant.outputs.each { output -&gt;

 def taskName = "taskindicate$output.name"
 task "$taskName"() &lt;&lt; {
 project.ext.set("currentConfig", "$output.name")
 }
 output.assemble.dependsOn "taskindicate$output.name"
 }
 }

}

task getConfig(dependsOn: ['installDebug', 'generateConfigProperty']) &lt;&lt; {
 println("My config is $currentConfig")
}
</code></pre>

took idea from the <a href="https://groups.google.com/d/msg/adt-dev/iSZuHNSdJHI/R8ZYF9486ecJ" rel="noreferrer">answer</a>

blocks|key|4581321|text|这个很简单：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4581322|android+{
++++applicationVariants.all+{+variant+->
++++++++variant.buildType.name+//+this+is+the+value!
++++}
}|code-block|syntax|javascript|4581323|编辑:显然，在gradle更新的某些时候，这并不像我在下面的评论中提到的那样工作。因此，我建议您选择其他选项。|4581324|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This one is quite simple:

<pre><code>android {
 applicationVariants.all { variant -&gt;
 variant.buildType.name // this is the value!
 }
}
</code></pre>

Edit: Apparently at some point with gradle update, this is not working as I mentioned in a comment below. So I'd recommend checking other options.

blocks|key|74905|text|//+declare+a+custom+task+class+so+you+can+reuse+it+for+the+different
//+variants
class+MyTask+extends+DefaultTask+{
+++++String+mVariantName;
+++++public+void+setVariantName(String+variant)+{mVariantName+=+variant;}
+++++public+String+getVariantName()+{+return+mVariantName;+}
+++++@TaskAction
+++++void+action(){
++++++++//+do+stuff
+++++}
}

//+put+this+after+your+`android{}`+block.
android.applicationVariants.all+{+variant+->
++++def+taskName+=+"myTask_$variant.name"
++++task+"$taskName"(type:+MyTask)+<<+{
++++++++//+you+can+setup+this+task+to+various+info+regarding
++++++++//+variant
++++++++variantName+=+variant.name
++++}
++++variant.assemble.dependsOn+(taskName)
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|74906|有关可以从variant变量提取的内容的更多详细信息，请参见Advance+customization。|unstyled|offset|length|style|CODE|74907|现在你可以正确地将你的MyTask连接到链上。这样做还可以清楚地处理一次构建多种风格的问题，因为它会为每个变体创建一个新的MyTask实例。|74908|entityMap|0|LINK|mutability|MUTABLE|url|http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Advanced-Build-Customization^0|0|5|7|U|L|0|0|B|6|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|V|8|@$G|W|H|X|I|J]]|9|@$G|Y|H|Z|1|10]]|A|$]]|$1|K|3|L|5|F|7|11|8|@$G|12|H|13|I|J]]|9|@]|A|$]]|$1|M|3|-4|5|F|7|14|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

<pre><code>// declare a custom task class so you can reuse it for the different
// variants
class MyTask extends DefaultTask {
 String mVariantName;
 public void setVariantName(String variant) {mVariantName = variant;}
 public String getVariantName() { return mVariantName; }
 @TaskAction
 void action(){
 // do stuff
 }
}

// put this after your `android{}` block.
android.applicationVariants.all { variant -&gt;
 def taskName = "myTask_$variant.name"
 task "$taskName"(type: MyTask) &lt;&lt; {
 // you can setup this task to various info regarding
 // variant
 variantName = variant.name
 }
 variant.assemble.dependsOn (taskName)
}
</code></pre>

See <a href="http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Advanced-Build-Customization" rel="nofollow">Advance customization</a> for more details of what you can extract from the <code>variant</code> variable.

now you it will properly hookup your <code>MyTask</code> into to the chain. Doing it this way should also cleanly handle building multiple flavors all at once as it creates a new instance of MyTask for each variant.

blocks|key|74926|text|您可以使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|74927|if+(gradle.startParameter.taskNames.contains("assembleExample"))+{
++++//+do+stuff
}|code-block|syntax|javascript|74928|该变量将在评估buildConfig块之前设置|offset|length|style|CODE|74929|entityMap^0|0|0|7|B|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You can use
<pre><code>if (gradle.startParameter.taskNames.contains(&quot;assembleExample&quot;)) {
 // do stuff
}
</code></pre>
That variable will be set before the <code>buildConfig</code> block is evaluated

blocks|key|74963|text|基于Shooky's+answer和JLund's+comment，这就是我的工作。我在我的应用程序build.gradle中有下面这段代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|74964|ext.getCurrentBuildType+=+{
++++def+isDebug+=+gradle.startParameter.taskRequests.any+{
++++++++++++++++++++++++++++it.args.any+{+it.endsWith("Debug")+}+}
++++return+isDebug+?+"Debug"+:+"Release"
}|code-block|syntax|javascript|74965|就叫它afterEvaluate吧。示例：|style|CODE|74966|afterEvaluate+{
++++tasks.getByName("externalNativeBuild${ext.getCurrentBuildType()}")
+++++++++.dependsOn+myOtherTask
}|74967|显然，gradle.startParameter有很多关于当前运行的信息。看一看doc。|74968|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/40876005/15139|1|https://stackoverflow.com/questions/25739163/how-to-get-current-buildtype-in-android-gradle-configuration/26335681#comment93900920_40876005|2|https://docs.gradle.org/current/javadoc/org/gradle/StartParameter.html^0|2|F|0|I|F|1|0|0|3|D|0|0|3|L|14|3|2|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]|$A|16|B|17|1|18]]|C|$]]|$1|D|3|E|5|F|7|19|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|1A|8|@$A|1B|B|1C|K|L]]|9|@]|C|$]]|$1|M|3|N|5|F|7|1D|8|@]|9|@]|C|$G|H]]|$1|O|3|P|5|6|7|1E|8|@$A|1F|B|1G|K|L]]|9|@$A|1H|B|1I|1|1J]]|C|$]]|$1|Q|3|-4|5|6|7|1K|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]|10|$5|T|U|V|C|$W|11]]]]

Based on <a href="https://stackoverflow.com/a/40876005/15139">Shooky's answer</a> and <a href="https://stackoverflow.com/questions/25739163/how-to-get-current-buildtype-in-android-gradle-configuration/26335681#comment93900920_40876005">JLund's comment</a>, this is what works for me. I have this code in my app build.gradle towards the end:
<pre><code>ext.getCurrentBuildType = {
 def isDebug = gradle.startParameter.taskRequests.any {
 it.args.any { it.endsWith(&quot;Debug&quot;) } }
 return isDebug ? &quot;Debug&quot; : &quot;Release&quot;
}
</code></pre>
Just call it <code>afterEvaluate</code>. Example:
<pre><code>afterEvaluate {
 tasks.getByName(&quot;externalNativeBuild${ext.getCurrentBuildType()}&quot;)
 .dependsOn myOtherTask
}
</code></pre>
Apparently, <code>gradle.startParameter</code> has plenty of info about current run. Take a look at the <a href="https://docs.gradle.org/current/javadoc/org/gradle/StartParameter.html" rel="nofollow noreferrer">doc</a>.

blocks|key|4581423|text|正在运行Gradle任务“assembleRelease”...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4581424|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Running Gradle task 'assembleRelease'...

I want to dynamically add a dependency in an Android Gradle project based on the current buildType. I know I can <a href="http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Library-Publication">specify the buildType in the dependency</a>:

<pre><code>compile project(path: ':lib1', configuration: 'debug')
</code></pre>

But how can I use the current buildType to specify which variant of the library I want to import, so that a debug or release build automatically imports the debug or release variant of the library? What I want is something like this (where currentBuildType is a variable containing the name of the currently used buildType):

<pre><code>compile project(path: ':lib1', configuration: currentBuildType)
</code></pre>

The library project I want to import has set <code>publishNonDefault true</code>, so all buildTypes are published.

How to get current buildType in Android Gradle configuration

Android

我想在基于当前buildType的Android Gradle项目中动态添加一个依赖项。我知道我可以compile project(path: ':lib1', configuration: 'debug')但是，如何使用当前的buildType指定要导入的库的哪个变体，以便调试或发布版本自动导入库的调试或发布变体？我...

问如何在Android Gradle配置中获取当前buildType
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Android Gradle配置中获取当前buildTypeEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Android Gradle配置中获取当前buildType
EN