Skip to content

Commit 1d80564

Browse files
authored
Add tracing and timing flags to readme.md (#585)
* adding tracing and timings flags to readme * Add tracing and timing flags to readme.md Added some markdown to include the flags --define=kt_trace=1 and --define=kt_timings=1 in the readme file. These reference issues #277 and #311. These two flags would help with any confusion and provide some documentation for them. @ulfjack @Yannic Signed-off-by: Bradley Burns <[email protected]>
1 parent 3e28470 commit 1d80564

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -263,6 +263,11 @@ kt_jvm_library(
263263
)
264264
```
265265

266+
Additionally, you can add options for both tracing and timing of the bazel build using the `kt_trace` and `kt_timings` flags, for example:
267+
* `bazel build --define=kt_trace=1`
268+
* `bazel build --define=kt_timings=1`
269+
270+
`kt_trace=1` will allow you to inspect the full kotlinc commandline invocation, while `kt_timings=1` will report the high level time taken for each step.
266271
# Kotlin compiler plugins
267272

268273
The `kt_compiler_plugin` rule allows running Kotlin compiler plugins, such as no-arg, sam-with-receiver and allopen.

0 commit comments

Comments
 (0)