jawt-binding

Kotlin/Native bindings for JAWT - the Java Abstract Window Toolkit native interface (jawt.h). The module wraps the C API into idiomatic Kotlin on top of jni-binding, so a native application can render into a java.awt.Component or hand a native window over to AWT without any manual cinterop configuration.

Desktop only (mingwX64, linuxX64, linuxArm64, macosArm64). Android has no AWT and is not a target of this module.

The module depends on jni-binding (and transitively on jni-binding-raw for the raw JDK headers), so everything from the JNI core - JniEnv, JNI, the null-safe reference types - is available as usual. Link libjawt with linkJAwt() of the producer plugin (call it after linkJvm(), which it reuses). On Linux also call linkX11IfLinux() when the AWT runtime needs X11.

These interfaces are not part of the Java SE specification; a VM is not required to implement them. See the JAWT documentation.

Kotlin/Native bindings for JAWT - the Java Abstract Window Toolkit native interface (jawt.h). The module wraps the C API into idiomatic Kotlin on top of jni-binding, so a native application can render into a java.awt.Component or hand a native window over to AWT without any manual cinterop configuration.

Desktop only (mingwX64, linuxX64, linuxArm64, macosArm64). Android has no AWT and is not a target of this module.

The module depends on jni-binding (and transitively on jni-binding-raw for the raw JDK headers), so everything from the JNI core - JniEnv, JNI, the null-safe reference types - is available as usual. Link libjawt with linkJAwt() of the producer plugin (call it after linkJvm(), which it reuses). On Linux also call linkX11IfLinux() when the AWT runtime needs X11.

These interfaces are not part of the Java SE specification; a VM is not required to implement them. See the JAWT documentation.

Kotlin/Native bindings for JAWT - the Java Abstract Window Toolkit native interface (jawt.h). The module wraps the C API into idiomatic Kotlin on top of jni-binding, so a native application can render into a java.awt.Component or hand a native window over to AWT without any manual cinterop configuration.

Desktop only (mingwX64, linuxX64, linuxArm64, macosArm64). Android has no AWT and is not a target of this module.

The module depends on jni-binding (and transitively on jni-binding-raw for the raw JDK headers), so everything from the JNI core - JniEnv, JNI, the null-safe reference types - is available as usual. Link libjawt with linkJAwt() of the producer plugin (call it after linkJvm(), which it reuses). On Linux also call linkX11IfLinux() when the AWT runtime needs X11.

These interfaces are not part of the Java SE specification; a VM is not required to implement them. See the JAWT documentation.

Kotlin/Native bindings for JAWT - the Java Abstract Window Toolkit native interface (jawt.h). The module wraps the C API into idiomatic Kotlin on top of jni-binding, so a native application can render into a java.awt.Component or hand a native window over to AWT without any manual cinterop configuration.

Desktop only (mingwX64, linuxX64, linuxArm64, macosArm64). Android has no AWT and is not a target of this module.

The module depends on jni-binding (and transitively on jni-binding-raw for the raw JDK headers), so everything from the JNI core - JniEnv, JNI, the null-safe reference types - is available as usual. Link libjawt with linkJAwt() of the producer plugin (call it after linkJvm(), which it reuses). On Linux also call linkX11IfLinux() when the AWT runtime needs X11.

These interfaces are not part of the Java SE specification; a VM is not required to implement them. See the JAWT documentation.

Kotlin/Native bindings for JAWT - the Java Abstract Window Toolkit native interface (jawt.h). The module wraps the C API into idiomatic Kotlin on top of jni-binding, so a native application can render into a java.awt.Component or hand a native window over to AWT without any manual cinterop configuration.

Desktop only (mingwX64, linuxX64, linuxArm64, macosArm64). Android has no AWT and is not a target of this module.

The module depends on jni-binding (and transitively on jni-binding-raw for the raw JDK headers), so everything from the JNI core - JniEnv, JNI, the null-safe reference types - is available as usual. Link libjawt with linkJAwt() of the producer plugin (call it after linkJvm(), which it reuses). On Linux also call linkX11IfLinux() when the AWT runtime needs X11.

These interfaces are not part of the Java SE specification; a VM is not required to implement them. See the JAWT documentation.