diff --git a/docs/html/tools/building/building-studio.jd b/docs/html/tools/building/building-studio.jd
index 8da70c0b9cb5e..7ba716fc3f424 100644
--- a/docs/html/tools/building/building-studio.jd
+++ b/docs/html/tools/building/building-studio.jd
@@ -548,21 +548,25 @@ parent.link=index.html
When you deploy a clean build, Android Studio instruments your app to allow
Instant Run to push code and resource updates. Although updating the running
app happens much more quickly, the first build may take longer to complete.
- You can improve the build process by configuring a few DEX options, such as
- maxProcessCount and javaMaxHeapSize.
+ You can improve the build process by configuring a few
+ DexOptions settings:
maxProcessCount
+
+ maxProcessCount
gradlew --stop
javaMaxHeapSize
+
+ javaMaxHeapSize
maxProcessCount to control how many slave dex processes can
- be spawned concurrently. The following code, in the module-level
+ maxProcessCount to control how many slave dex processes can be
+ spawned concurrently. The following code, in the module-level
build.gradle file, sets the maximum number of concurrent processes
to 4:
android {
...
dexOptions {
- maxProcessCount = 4
+ maxProcessCount = 4 // this is the default value
}
}
@@ -192,11 +200,11 @@ android {
...
buildTypes {
debug {
- minifyEnabed true
+ minifyEnabled true
useProguard false
}
release {
- minifyEnabed true
+ minifyEnabled true
useProguard true // this is a default setting
}
}