android studio+grade配置构建
发布时间：2017-06-02 08:13:02 所属栏目：安卓资讯 来源：www.yidianzixun.com
导读：Android构建系统编译应用资源和源代码，然后将它们打包成可供您测试、部署、签署和分发的APK。AndroidStudio使用Gradle这一高级构建工具包来自动化执行和管理构建流程，同时也允许您定义灵活的自定义构建配置。每个构建配置均...
|
有几个 Gradle构建配置文件是 Android应用标准项目结构的组成部分。您必须了解其中每一个文件的范围和用途及其应定义的基本 DSL元素，才能着手配置构建。 Gradle设置文件settings.gradle文件位于项目根目录，用于指示 Gradle在构建应用时应将哪些模块包括在内。对大多数项目而言，该文件很简单，只包括以下内容：include ‘:app’不过，多模块项目需要指定应包括在最终构建之中的每个模块。 顶级构建文件顶级build.gradle文件位于项目根目录，用于定义适用于项目中所有模块的构建配置。默认情况下，这个顶级构建文件使用 buildscript {}代码块来定义项目中所有模块共用的 Gradle 存储区和依赖项。以下代码示例描述的默认设置和 DSL元素可在新建项目后的顶级 build.gradle文件中找到。/** * The buildscript {} block is where you configure the repositories and * dependencies for Gradle itself--meaning, you should not include dependencies * for your modules here. For example, this block includes the Android plugin for * Gradle as a dependency because it provides the additional instructions Gradle * needs to build Android app modules. */ buildscript {/** * The repositories {} block configures the repositories Gradle uses to * search or download the dependencies. Gradle pre-configures support for remote * repositories such as JCenter, Maven Central, and Ivy. You can also use local * repositories or define your own remote repositories. The code below defines * JCenter as the repository Gradle should use to look for its dependencies. */ repositories { jcenter}/** * The dependencies {} block configures the dependencies Gradle needs to use * to build your project. The following line adds Android Plugin for Gradle * version 2.3.2 as a classpath dependency. */ dependencies { classpath 'com.android.tools.build:gradle:2.3.2'}}/** * The allprojects {} block is where you configure the repositories and * dependencies used by all modules in your project, such as third-party plugins * or libraries. Dependencies that are not required by all the modules in the * project should be configured in module-level build.gradle files. For new * projects, Android Studio configures JCenter as the default repository, but it * does not configure any dependencies. */ allprojects { repositories { jcenter}}模块级构建文件模块级文件位于每个 /目录，用于配置适用于其所在模块的构建设置。您可以通过配置这些构建设置来提供自定义打包选项（例如附加构建类型和产品风味），以及替换main/应用清单或顶级 build.gradle文件中的设置。以下这个示例 Android应用模块 build.gradle文件概述了您应该了解的部分基本 DSL元素和设置。/** * The first line in the build configuration applies the Android plugin for * Gradle to this build and makes the android {} block available to specify * Android-specific build options. */ apply plugin:'com.android.application'/** * The android {} block is where you configure all your Android-specific * build options. */ android {/** * compileSdkVersion specifies the Android API level Gradle should use to * compile your app. This means your app can use the API features included in * this API level and lower. * * buildToolsVersion specifies the version of the SDK build tools, command-line * utilities, and compiler that Gradle should use to build your app. You need to * download the build tools using the SDK Manager. */ compileSdkVersion 25 buildToolsVersion "25.0.3"/** * The defaultConfig {} block encapsulates default settings and entries for all * build variants, and can override some attributes in main/AndroidManifest.xml * dynamically from the build system. You can configure product flavors to override * these values for different versions of your app. */ defaultConfig {/** * applicationId uniquely identifies the package for publishing. * However, your source code should still reference the package name * defined by the package attribute in the main/AndroidManifest.xml file. */ applicationId 'com.example.myapp'// Defines the minimum API level required to run the app. minSdkVersion 15// Specifies the API level used to test the app. targetSdkVersion 25// Defines the version number of your app. versionCode 1// Defines a user-friendly version name for your app. versionName "1.0"}/** * The buildTypes {} block is where you can configure multiple build types. * By default, the build system defines two build types: debug and release. The * debug build type is not explicitly shown in the default build configuration, * but it includes debugging tools and is signed with the debug key. The release * build type applies Proguard settings and is not signed by default. */ buildTypes {/** * By default, Android Studio configures the release build type to enable code * shrinking, using minifyEnabled, and specifies the Proguard settings file. */ release { minifyEnabled true// Enables code shrinking for the release build type. proguardFiles getDefaultProguardFile('proguard-android.txt'),'proguard-rules.pro'}}/** * The productFlavors {} block is where you can configure multiple product * flavors. This allows you to create different versions of your app that can * override defaultConfig {} with their own settings. Product flavors are * optional, and the build system does not create them by default. This example * creates a free and paid product flavor. Each product flavor then specifies * its own application ID, so that they can exist on the Google Play Store, or * an Android device, simultaneously. */ productFlavors { free { applicationId 'com.example.myapp.free'} paid { applicationId 'com.example.myapp.paid'}}/** * The splits {} block is where you can configure different APK builds that * each contain only code and resources for a supported screen density or * ABI. You'll also need to configure your build so that each APK has a * different versionCode. */ splits {// Screen density split settings density {// Enable or disable the density split mechanism enable false// Exclude these densities from splits exclude "ldpi""tvdpi""xxxhdpi""400dpi""560dpi"}}}/** * The dependencies {} block in the module-level build configuration file * only specifies dependencies required to build the module itself. */ dependencies { compile project(":lib") compile 'com.android.support:appcompat-v7:25.3.1' compile fileTree(dir:'libs' include:['*.jar'])}Gradle属性文件（编辑：无忧刷机网 - 51刷机网） 【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容! |