From 39d6d1dec28b97144aa8f39406c0dd3fe98dbb03 Mon Sep 17 00:00:00 2001 From: Svyatoslav Scherbina Date: Thu, 28 Nov 2024 13:06:06 +0100 Subject: [PATCH] fixup! update: clarify release build in native-improving-compilation-time.md --- docs/topics/native/native-improving-compilation-time.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/native/native-improving-compilation-time.md b/docs/topics/native/native-improving-compilation-time.md index ab5593d66a8..0babc92afeb 100644 --- a/docs/topics/native/native-improving-compilation-time.md +++ b/docs/topics/native/native-improving-compilation-time.md @@ -63,7 +63,7 @@ Here are some recommendations for configuring Gradle for better compilation perf {style="tip"} * **Don't build release binaries unless necessary**. Kotlin/Native supports - [two build modes – debug and release](https://kotlinlang.org/docs/multiplatform-build-native-binaries.html#declare-binaries). + [two build modes – debug and release](multiplatform-build-native-binaries.md#declare-binaries). Release is highly optimized, and this takes a lot of time: compilation of release binaries takes an order of magnitude more time than debug binaries. In a typical development cycle, all the optimizations might be unnecessary. So, if your development cycle uses a task with "Release" in its name, consider replacing it with "Debug". Similarly, instead