メニュー
Use when building Vala projects with xmake — `.vala` sources with the `add_rules("vala")` rule, glib dependency, declaring used VAPI packages with `add_values("vala.packages", ...)`, and producing executables or shared/static libraries with exported headers/VAPIs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use 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.
| name | xmake-vala |
| description | Use when building Vala projects with xmake — `.vala` sources with the `add_rules("vala")` rule, glib dependency, declaring used VAPI packages with `add_values("vala.packages", ...)`, and producing executables or shared/static libraries with exported headers/VAPIs. |
Vala compiles to C (via valac), then to native code. Xmake handles both steps via the vala rule. Supported since v2.5.7 (binaries) / v2.5.8 (libraries).
add_rules("mode.debug", "mode.release")
add_requires("glib") -- mandatory
target("hello")
set_kind("binary")
add_rules("vala") -- required
add_files("src/*.vala")
add_packages("glib")
add_values("vala.packages", "glib-2.0", "gobject-2.0")
Three things every Vala target needs:
add_rules("vala") — tells xmake this is a Vala target.add_requires("glib") + add_packages("glib") — Vala's runtime.add_values("vala.packages", ...) — the VAPI package names that valac should import.target("mymath")
set_kind("static")
add_rules("vala")
add_files("src/*.vala")
add_packages("glib")
add_values("vala.packages", "glib-2.0", "gobject-2.0")
add_values("vala.header", "mymath.h") -- exported C header
add_values("vala.vapi", "mymath-1.0.vapi") -- exported VAPI
Consumers in C can #include "mymath.h"; consumers in Vala import mymath-1.0.vapi.
target("mymath")
set_kind("shared")
add_rules("vala")
add_files("src/*.vala")
add_packages("glib")
add_values("vala.packages", "glib-2.0", "gobject-2.0")
add_values("vala.header", "mymath.h")
add_values("vala.vapi", "mymath-1.0.vapi")
target("app")
set_kind("binary")
add_files("src/main.c")
add_deps("mymath")
add_packages("glib")
The exported header and VAPI flow through add_deps automatically.
add_rules("vala"). .vala files are treated as unknown — build fails. Always add the rule.vala.packages vs add_packages. These are different axes: vala.packages is what valac imports (VAPI names), add_packages is what xmake links. You usually need both for glib.glib-2.0, not glib. Check pkg-config --list-all for the exact names.xmake-packagesxmake-targets