commit | 907768e8b9d74b0c31355abe5b4227a44ff46998 | [log] [tgz] |
---|---|---|
author | Hassan Syed <h.a.syed@gmail.com> | Fri Sep 14 01:19:31 2018 +0100 |
committer | GitHub <noreply@github.com> | Fri Sep 14 01:19:31 2018 +0100 |
tree | f265fe403714f06db3b202f4021c7d0dbc53e2e5 | |
parent | c56299c32437cf9608612868beb1c2ba9386940d [diff] |
update to 1.2.70 and remove friend paths work arround (#142)
examples/node
.kotlin/internal/jvm/android.bzl
.>=0.14
. JDK9 host issues were fixed as well some other deprecations. I recommend skipping 0.15.0
if you are on a Mac.kt_jvm_test
which allows the test to access internal members of the module under test.kotlin_
to kt_jvm_
.These rules were initially forked from pubref/rules_kotlin. Key changes:
kt_jvm_binary
, kt_jvm_library
and kt_jvm_test
.java_dep
and dep
.data
resource_jars
runtime_deps
resources
resources_strip_prefix
exports
This section just contains a quick overview. Consult the generated documentation. Note: Skydoc documentation is no longer being generated. Comprehensive documentation will have to wait till the new documentation generation tool is ready. A contribution to port the documentation to the RST format like rules_go
has would be very welcome !
In the project's WORKSPACE
, declare the external repository and initialize the toolchains, like this:
rules_kotlin_version = "67f4a6050584730ebae7f8a40435a209f8e0b48e" http_archive( name = "io_bazel_rules_kotlin", urls = ["https://github.com/bazelbuild/rules_kotlin/archive/%s.zip" % rules_kotlin_version], type = "zip", strip_prefix = "rules_kotlin-%s" % rules_kotlin_version ) load("@io_bazel_rules_kotlin//kotlin:kotlin.bzl", "kotlin_repositories", "kt_register_toolchains") kotlin_repositories() kt_register_toolchains()
In your project's BUILD
files, load the kotlin rules and use them like so:
load("@io_bazel_rules_kotlin//kotlin:kotlin.bzl", "kt_jvm_library") kt_jvm_library( name = "package_name", srcs = glob(["*.kt"]), deps = [ "//path/to/dependency", ], )
This project is licensed under the Apache 2.0 license, as are all contributions
See the CONTRIBUTING doc for information about how to contribute to this project.