Android的工作室：为什么的minSdkVersion和targetSdkVersion无论是在AndroidManifest.xml中和build.gradle规定？ [英] Android studio: why are minSdkVersion and targetSdkVersion specified both in AndroidManifest.xml and build.gradle?

问题描述

我刚刚发现了一些奇怪的关于Android的工作室：它在 build.gradle 文件覆盖了 AndroidManifest中指定的一些配置选项的.xml 文件。

I just discovered something weird about Android studio: it has some configuration options in the build.gradle file that override what is specified in the AndroidManifest.xml file.

例如，我在下面的行 build.gradle ：

android {
    compileSdkVersion 18
    buildToolsVersion "18.1.1"

    defaultConfig {
        minSdkVersion 10
        targetSdkVersion 10
    }
...
}

这是压倒一切的的Andr​​oidManifest.xml 相应的标记：

<uses-sdk
    android:minSdkVersion="8"
    android:targetSdkVersion="8"/>

我真的不喜欢有相同的设置•$ P $垫在两个不同的文件，所以我想知道如果我可以有把握地无论是从 build.gradle 或的Andr​​oidManifest.xml 和它更有意义，以保持它。

I don't really like to have the same settings spread in two different files, so I am wondering if I can safely remove it either from build.gradle or AndroidManifest.xml and where it makes more sense to keep it.

推荐答案

摇篮覆盖清单价值观，我preFER更新build.gradle文件，而不是清单。而这很可能是用摇篮的正确途径。摇篮支持可通过IDE得以控制以及产品的口味可以在我们的清单像包的名称，版本code，版本名称改变很多事情，目标SDK和许多其他产品的口味。然后，通过点击在Android的Studio中您可以更改许多属性，并生成另一个APK。

Gradle overrides the manifest values, and I prefer to update build.gradle file rather than manifest. And probably this is the right way using Gradle. Gradle supports product flavours which can be controled via IDE and those product flavors can change many things in our Manifest like package name, version code, version name, target SDK and many other. Then by one click in Android Studio You can change many properties and generate another apk.

您可以留下明显的，因为它是做所有配置中build.gradle。您可以安全地删除

You can left the manifest as it is and do all configuration in build.gradle. You can safely remove

<uses-sdk></uses-sdk>

从清单以及版本codeS。

from manifest as well as version codes.

这篇关于Android的工作室：为什么的minSdkVersion和targetSdkVersion无论是在AndroidManifest.xml中和build.gradle规定？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！