You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* 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]>
Copy file name to clipboardExpand all lines: README.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -263,6 +263,11 @@ kt_jvm_library(
263
263
)
264
264
```
265
265
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.
266
271
# Kotlin compiler plugins
267
272
268
273
The `kt_compiler_plugin` rule allows running Kotlin compiler plugins, such as no-arg, sam-with-receiver and allopen.
0 commit comments