メニュー
Use when building Kotlin/Native projects with xmake — `.kt` sources for native (not JVM) targets, using the `kotlin-native` toolchain, producing executables and static/shared libraries.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | xmake-kotlin |
| description | Use when building Kotlin/Native projects with xmake — `.kt` sources for native (not JVM) targets, using the `kotlin-native` toolchain, producing executables and static/shared libraries. |
Xmake's Kotlin support targets Kotlin/Native — the ahead-of-time-compiled flavor, not JVM. For JVM-side projects, use Gradle/Maven directly.
xmake create -l kotlin -t console hello
cd hello
xmake run
add_rules("mode.debug", "mode.release")
target("hello")
set_kind("binary")
add_files("src/*.kt")
target("app") set_kind("binary") -- Kotlin/Native executable
target("mylib") set_kind("static")
target("mydyn") set_kind("shared")
Kotlin/Native must be installed separately — it's not bundled with xmake.
xmake f --toolchain=kotlin-native
xmake f --toolchain=kotlin-native --sdk=/opt/kotlin-native-prebuilt-linux-x86_64-1.9.0
Download the compiler from kotlinlang.org/docs/native-overview.html and point --sdk at it.
Kotlin/Native supports many platforms:
xmake f -p linux -a x86_64 --toolchain=kotlin-native
xmake f -p macosx -a arm64 --toolchain=kotlin-native
xmake f -p windows -a x86_64 --toolchain=kotlin-native
xmake f -p iphoneos -a arm64 --toolchain=kotlin-native
Kotlin/Native has a cinterop mechanism for binding C libraries. At the xmake level, link native static libs the usual way:
target("app")
set_kind("binary")
add_files("src/*.kt")
add_deps("mycdep") -- C static library target
cinterop configuration (the .def files) is Kotlin-side — see Kotlin/Native docs.
--sdk globally via xmake g --sdk=....xmake-targetsxmake-cross-compilationUse when switching xmake's output theme (colors, progress style, emoji) or fixing garbled/unreadable terminal output — `xmake g --theme=...`. Built-in themes: default, ninja, emoji, dark, light, plain, powershell.
Use when the user is starting a new Xmake project, installing Xmake, or needs the minimal xmake.lua structure. Covers installation, `xmake create`, the project layout, and the smallest valid xmake.lua.
Use when writing or reviewing an `xmake.lua` (project, package recipe, or toolchain) and you want to follow idiomatic xmake style — description vs script domain separation, naming, indentation, `set_` vs `add_`, option/config organization, and common conventions used across xmake-repo and the xmake project itself. Apply this alongside `xmake-targets`/`xmake-packages`/etc. as a stylistic overlay.
Use when creating a new xmake project from a built-in or third-party template (`xmake create -t <template>`), listing available templates, or authoring and distributing custom templates (built-in, user-global, or via xmake-repo). Covers template layout, `${TARGET_NAME}` / `${FAQ}` substitution, and language selection.
Use when invoking Xmake from the command line — configuring, building, running, cleaning, installing, packing, or inspecting a project. Covers the common flags for `xmake f`, `xmake`, `xmake run`, `xmake install`, `xmake pack`, and friends.
Use when exporting an xmake project to another build system or IDE — `compile_commands.json` for clangd/LSP, `CMakeLists.txt`, `build.ninja`, Visual Studio solution (`vsxmake`), or an Xcode project. Covers `xmake project -k <kind>` and how each generator is typically used.