Make the protobuf dependencies lazy or use precompiled archives. about rules_kotlin HOT 4 CLOSED

Closed by #30

from rules_kotlin.

Hi @hsyed the bazel worker code introduced this step.
e82156d. It makes the compilation of kotlin faster and internally uses protobuf for communication/serialization with bazel itself, and so does require all that initial setup.

I think it would be possible to make use of the bazel worker optional.

from rules_kotlin.

@pcj Fast is always good :D -- the Kotlin build do have a longer turn around than java builds though. I noticed the kotlin build uses the Kotlin Console ? Without the worker it will probably be unbearable.

Would it be possible to use packaged versions of the dependencies (http_archive) ? Other rules must be making use of this feature. Might be able to borrow the packaged packaged dependency logic, (the Scala rules maybe).

from rules_kotlin.

@hsyed I checked in the generated proto and removed dependencies on the protobuf compiler. Should be fine as the worker.proto file will change very infrequently if at all.

A clean run of bazel run //examples/helloworld:main_kt following bazel clean --expunge is now 30s vs 2m30s on my machine. Assuming travis passes will merge shortly.

See #30

from rules_kotlin.