| commit | cd3aa604316fa5c6c9486f2cb9caa3eaccd74476 | [log] [tgz] |
|---|---|---|
| author | Xavier Ducrohet <xav@android.com> | Fri Dec 07 18:50:44 2012 -0800 |
| committer | Xavier Ducrohet <xav@android.com> | Mon Dec 10 17:01:07 2012 -0800 |
| tree | 38455d4e69fb7dd84b1a8647b8f6289a61c60486 | |
| parent | 3b49b176fcbfe1bbae0f63f769a39a3cb41c79ef [diff] |
Use the ResourceMerger to handle overlay. This creates a merged res folder that is then fed to aapt. Right now the merged folder does not have its image crunched, nor is it incremental. This means the build will be slower (previously crunching was incremental). Next step is to change aapt to be able to crunch single images and then make the merging itself incremental. Details: The processImage task is replaced by mergeResourceTask. It is also used for library project that had to merge their resources before bundling, so the previous copy task is removed and the merge is done directly in the bundle folder. The API for AndroidBuilder is changed to reflect those changes. processResource now only takes one res folder which is meant to be the merged one. The getResourceInputs on VariantConfig is changed to return a list of ResourceSets (except not actual ResourceSet since this would load the resources, so instead a list of list of files). Also changed build.gradle for the gradle plugin to have the integration test first deploy the plugin locally in order to use the right one. Change-Id: Ide96f733be835d94518b831baee7ee77b9a61dec
A prototype Gradle plugin to build Android applications. This is intended to be used to explore how such a plugin would look and to develop some ideas about how such a plugin would be implemented.
The plugin is functional, if a bit rough, and can generate packaged applications ready to install.
The plugin adds 2 concepts to the Gradle DSL:
release and debug. You can add additional build types.If you do not define any flavors for your product, a default flavor called main is added.
From this, the plugin will add the appropriate tasks to build each combination of build type and product flavor. The plugin will also define the following source directories:
src/main/java - Java source to be included in all application variants.src/main/res - Resources to be included in all application variants.src/$BuildType/java - Java source to be included in all application variants with the given build type.src/$BuildType/res - Java source to be included in all application variants with the given build type.src/$ProductFlavor/java - Resources to be included in all application variants with the given product flavor.src/$ProductFlavor/res - Resources to be included in all application variants with the given product flavor.src/test/java - Test source to be included in all test applications.src/test$ProductFlavor/java - Test source to be include for the test application for the given product flavor.You can configure these locations by configuring the associated source set.
Compile time dependencies are declared in the usual way.
Have a look at the basic/build.gradle and customized/build.gradle build files to see the DSL in action.
android.packageName - defaults to that specified in src/main/AndroidManifest.xmlandroid.versionCode - defaults to that specified in src/main/AndroidManifest.xmlandroid.versionName - defaults to that specified in src/main/AndroidManifest.xmlandroid.target - defaults to android-16.android.productFlavors.$flavor.packageName - defaults to ${android.packageName}android.productFlavors.$flavor.versionCode - defaults to ${android.versionCode}android.productFlavors.$flavor.versionName - defaults to ${android.versionName}android.buildTypes.$type.zipAlign - defaults to true for release and false for debugsourceSets.main.java.srcDirs - defaults to src/main/javasourceSets.main.resources.srcDirs - defaults to src/main/ressourceSets.$flavor.java.srcDirs - defaults to src/$flavor/javasourceSets.$flavor.resources.srcDirs - defaults to src/$flavor/ressourceSets.$buildType.java.srcDirs - defaults to src/$buildType/javasourceSets.$buildType.resources.srcDirs - defaults to src/$buildType/ressourceSets.test.java.srcDirs - defaults to src/test/javasourceSets.test$Flavor.java.srcDirs - defaults to src/test$Flavor/javadependencies.compile - compile time dependencies for all applications.The source tree contains the following:
gradle directory contains the plugin implementation.testapps/basic directory contains a simple application that follows the conventionstestapps/customized directory contains an application with some custom build types, product flavors and other customizations.testapps/multiproject directory contains an application composed from several Gradle projects.To build the plugin, run ./gradlew uploadArchives
To import the plugin into the IDE, run ./gradlew idea or ./gradlew eclipse.
To build a test application:
local.properties file to point at your local install of the Android SDK. Normally, these files would not be checked into source control, but would be generated when the project is bootstrapped.../../gradlew tasks to see the tasks that are available.You can also run these tasks:
assemble - builds all combinations of build type and product flavorassemble$BuildType - build all flavors for the given build type.assemble$ProductFlavor - build all build types for the given product flavor.assemble$ProductFlavor$BuildType - build the given application variant.install$ProductFlavor$BuildType - build and install the given application variant.For each variant (product-flavor, build-type):
build/source from resource directories (main-source-set, product-flavor-source-set, build-type-source-set)build/libsbuild/resourcesbuild/libsbuild/libs.Some other notes:
sourceSets.main.compileClasspath as the compile classpath for each variant. Could potentially also include sourceSets.$BuildType.compileClasspath and sourceSets.$ProductFlavor.compileClasspath as well.