解决Gradle build finished with 744 error(s) in 4m 33s 896ms。同时加快build apk即生成app的过程

来源:互联网 发布:2016天猫双11实时数据 编辑:程序博客网 时间:2024/05/17 08:22

 Gradle build finished with 744 error(s) in 4m 33s 896ms


这个问题的原因是虚拟机的空间不足。


解决办法:

在根目录,比如下图的gradle.properties中增加,如果没有gradle.properties,就new files自己新建一个。

增加的代码在这里

# Project-wide Gradle settings.# IDE (e.g. Android Studio) users:# Settings specified in this file will override any Gradle settings# configured through the IDE.# For more details on how to configure your build environment visit # http://www.gradle.org/docs/current/userguide/build_environment.html # The Gradle daemon aims to improve the startup and execution time of Gradle.# When set to true the Gradle daemon is to run the build.# TODO: disable daemon on CI, since builds should be clean and reliable on servers org.gradle.daemon=true# Specifies the JVM arguments used for the daemon process.# The setting is particularly useful for tweaking memory settings.# Default value: -Xmx7168m -XX:MaxPermSize=256m org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8# When configured, Gradle will run in incubating parallel mode.# This option should only be used with decoupled projects. More details, visit #http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects org.gradle.parallel=true# Enables new incubating mode that makes Gradle selective when configuring projects.# Only relevant projects are configured which results in faster builds for large multi-projects.#http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:configuration_on_demand org.gradle.configureondemand=true
其中

Default value: -Xmx7168m

这句话控制大小,我让他为7G。不够你再给,反正要大于报错提示给的大小。



同时这样也可以加快app的打包速度。如果你有固态硬盘,那就更快了。我没有固态硬盘,也从一开始5-10分钟一个到了现在,2分钟以内能运行一次。

0 0
原创粉丝点击