README.md

Kotlin Rules for Bazel

Note: These rules require Bazel 0.3.1 or higher.

These rules are for building Kotlin source with with Bazel.

1. kotlin_repositories
2. kotlin_library
3. kotlin_binary

Workspace rules

Add the following to your WORKSPACE file:

git_repository(
    name = "org_pubref_rules_kotlin",
    remote = "https://github.com/pubref/rules_kotlin.git",
    tag = "v0.2.3", # update as needed
)
load("@org_pubref_rules_kotlin//kotlin:rules.bzl", "kotlin_repositories")
kotlin_repositories()

This will fetch a release (currently 1.1.2-2) and expose the shell scripts and the runtime library.

bazel query @com_github_jetbrains_kotlin//... --output label_kind
# The kotlin runtime jar
java_import rule @com_github_jetbrains_kotlin//:runtime
# Script for the compiler
sh_binary rule @com_github_jetbrains_kotlin//:kotlinc
# Script for the runner
sh_binary rule @com_github_jetbrains_kotlin//:kotlin

Package (BUILD file) rules

Add the following to your BUILD file:

load("@org_pubref_rules_kotlin//kotlin:rules.bzl", "kotlin_library", "kotlin_binary")

kotlin_library

Example:

kotlin_library(
    name = "my_kotlin_lib",
    srcs = ["kotlin_source_file.kt"],
    deps = [":some_other_kotlin_library_rule"],
    java_deps = [":some_other_java_library_rule", "@another_maven_jar//jar"],
)

Use the deps attribute to name other kotlin_library targets as jar providers for this rule. Use the java_deps attribute to name other java_library or java_import targets (to expose traditional java classes in your kotlin source).

To compile a set of kotlin sources files with the kotlinc tool and emit the corresponding jar file, use:

$ bazel build :my_kotlin_lib
Target :my_kotlin_lib up-to-date:
  bazel-bin/.../my_kotlin_lib.jar

To use the output of a kotlin_library as input to a java_library rule (and make your compiled kotlin classes available to your traditional java source files), name it as a dependency using the deps attribute, just as you would any other java_library target. The name of this target must be of the form {kotlin_library_target_name}_kt. For example, to use the :my_kotlin_lib in an android_binary target, the name would be :my_kotlin_lib_kt, such as:

android_binary(
   name = "foo",
   deps = [
       ":my_kotlin_lib_kt`,
   ]
)

kotlin_library attributes

Name	Type	Description
srcs	label_list	Kotlin source files *.kt
deps	label_list	List of kotlin_library targets
java_deps	label_list	List of java provider targets (java_library, java_import, ...)
jars	label_list	List of jar file targets (*.jar)
x_opts	string_list	List of additional -X options to kotlinc
plugin_opts	string_dict	List of additional -P options to kotlinc

kotlin_binary

A kotlin_binary rule takes the same arguments as a kotlin_library, plus a required main_class argument (the name of the compiled kotlin class to run, in java package notation). This class should have a fun main(...) entrypoint. Example:

kotlin_binary(
    name = "main_kt",
    main_class = "my.project.MainKt",
    srcs = ["main.kt"],
    deps = [":my_kotlin_lib"]
    java_deps = [":javalib"]
)

To create a self-contained executable jar, invoke the implicit _deploy.jar target. For example:

$ bazel build :main_kt_deploy.jar
Target :main_kt_deploy.jar up-to-date:
  bazel-bin/.../main_kt_deploy.jar
$ java -jar ./bazel-bin/.../main_kt_deploy.jar

kotlin_binary attributes

Includes all kotlin_library attributes as well as:

Name	Type	Description
main_class	string	Main class to run with the kotlin_binary rule

kotlin_compile

The kotlin_compile rule runs the kotlinc tool to generate a .jar file from a list of kotlin source files. The kotlin_library rule (actually, macro) calls this internally and then makes the jarfile available to other java rules via a java_import rule.

In summary, you most likely do not need to interact with the kotlin_compile rule directly.

bazel.rc

With older versions of bazel, you may need to add the following line to your tools/bazel.rc file:

build --strategy=KotlinCompile=standalone

Alternatively, you can also add --strategy=KotlinCompile=standalone parameters to every bazel run, bazel build, etc. commands involving a kotlin rule.

Summary

That's it! Hopefully these rules with make it easy to mix kotlin and traditional java code in your projects and take advantage of bazel's approach to fast, repeatable, and reliable builds.

Note: if you have a bunch of maven (central) dependencies, consider rules_maven for taming the issue of transitive dependencies with your java/kotlin projects.

Examples

To run the examples in this repository, clone the repo:

$ git clone https://github.com/pubref/rules_kotlin
$ cd rules_kotlin
$ bazel query //... --output label_kind
$ bazel run examples/helloworld:main_kt
$ bazel run examples/helloworld:main_java

TODO

1. Implement a kotlin_test rule.
2. Proper data and runfiles support.
3. Research incremental compilation and bazel worker integration.
4. kapt integration.