Skip to content

Commit 5a5293e

Browse files
docs: regenerate llms.txt and llms-full.txt
1 parent 3a0169f commit 5a5293e

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/llms-full.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3167,7 +3167,7 @@ import io.github.kdroidfilter.nucleus.aot.runtime.ExecutableRuntime
31673167

31683168
# GraalVM Native Image
31693169

3170-
**Experimental — for advanced developers only:** GraalVM Native Image compilation for Compose Desktop is **highly experimental**. If reflection is not fully resolved at build time, the application **will crash at runtime**. This mode requires significant effort to configure and debug. Proceed only if you are comfortable with native-image internals.
3170+
**Alpha:** GraalVM Native Image support is **in alpha**. Most Compose Desktop apps work out of the box thanks to centralized reachability metadata, but edge cases (uncommon libraries, custom reflection) may still require additional configuration.
31713171
## Why Native Image?
31723172

31733173
For most Compose Desktop applications, [AOT Cache (Leyden)](../runtime/aot-cache.md) is the recommended way to improve startup. It's simple to set up and provides a major boost. But there are cases where even Leyden isn't enough:
@@ -3189,7 +3189,7 @@ Native image is not a free lunch. In addition to significantly more complex conf
31893189
| CPU throughput | Excellent (JIT) | Lower (no JIT) |
31903190
| Bundle size | Larger (includes JRE) | Smaller |
31913191
| Configuration | Simple (`enableAotCache = true`) | Simplified (centralized metadata) |
3192-
| Stability | Stable | Experimental |
3192+
| Stability | Stable | Alpha |
31933193

31943194
**Choose native image when** startup speed and memory footprint are critical and CPU throughput is secondary. **Choose Leyden when** you want the best balance of performance, simplicity, and stability.
31953195

@@ -10104,7 +10104,7 @@ Standard OpenJDK does not detect the native display scale factor on Linux. On Hi
1010410104

1010510105
The `linux-hidpi` module provides native scale factor detection using JNI, mirroring the detection logic built into JetBrains Runtime (`systemScale.c`). It queries multiple system sources and returns the correct scale so you can apply it via `sun.java2d.uiScale` before AWT initialises.
1010610106

10107-
This module was originally designed for running Compose Desktop applications compiled with **GraalVM Native Image** (experimental), where JBR is not available and scale detection must be handled manually.
10107+
This module was originally designed for running Compose Desktop applications compiled with **GraalVM Native Image** (alpha), where JBR is not available and scale detection must be handled manually.
1010810108

1010910109
**JBR recommended for JVM-based applications:** If your application runs on a standard JVM (not a native image), prefer using **JetBrains Runtime (JBR)** which handles HiDPI detection natively and provides stable, battle-tested support across Linux desktop environments. This module is only necessary when JBR is not an option — typically with GraalVM Native Image or other non-JBR runtimes.
1011010110
**Already handled by `GraalVmInitializer`:** If you use the [`graalvm-runtime`](../graalvm/runtime-bootstrap.md) module, `GraalVmInitializer.initialize()` already calls `getLinuxNativeScaleFactor()` and applies the scale factor automatically. You do **not** need to add `linux-hidpi` as a separate dependency or call the function manually — it is included transitively.

0 commit comments

Comments
 (0)