Closed hpsaturn closed 6 years ago
I'm not sure that the issue is related to jack. When you do a build from clean you have to recreate classes from the Protobufs. That compilation process will take longer than a normal Android compilation.
I agree, but this is the point, never it cached the binaries, all compilations have the same time (the next compilations to first), it is a big nightmare, when disabling jack, everything goes back to normal.
When I do a clean, I expect that the binaries are deleted and need to be regenerated from scratch. I have not been able to reproduce any abnormally long compilation times with a simple rebuild
My system operative and more settings are the next:
org.gradle.daemon=true
org.gradle.parallel=true
org.gradle.jvmargs=-Xmx2048m -XX:MaxPermSize=512m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8
blank
(empty)Source code (My fork): Google Assistant code for MATRIX Creator
Can you compile the protobufs into Java classes, then copy those classes to new files and disable the protobuf generation? I think that without that step the compilation should be faster.
But without the jack options works fine and very fast, for this I reported this issue.
I think we may be able to get rid of the jack dependencies now that the grpc
code is broken out in a separate module.
It doesn't seem like we're using Jack now.
Hi,
Ever, with each compilation the project take the same time like a build after clean. The solution take from ~4 min to 15 secs with each build. The solution is comment the next options:
Tools: AndroidStudio 2.3.3 stable channel. Repository same to master.