القائمة
Use when adding third-party C/C++ dependencies to an Xmake project — via `add_requires` / `add_packages`, configuring package options, pinning versions, or using `xrepo` from the command line.
التثبيت باستخدام 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-packages |
| description | Use when adding third-party C/C++ dependencies to an Xmake project — via `add_requires` / `add_packages`, configuring package options, pinning versions, or using `xrepo` from the command line. |
Xmake has a built-in package manager (xrepo) that fetches and builds C/C++ dependencies and wires them into your targets.
add_requires("fmt 10.2.1", "spdlog")
target("app")
set_kind("binary")
add_files("src/*.cpp")
add_packages("fmt", "spdlog")
add_requires declares what you need (and optionally a version). add_packages attaches the package to a specific target, adding its includes, links, and defines automatically.
add_requires("zlib 1.3.x") -- semver range
add_requires("openssl >=3.0")
add_requires("cmake master") -- branch
add_requires("boost 1.84.0")
add_requires("boost", {configs = {regex = true, system = true, shared = false}})
add_requires("ffmpeg", {configs = {shared = true, gpl = false}})
Options map to the package's own configurable features — check the package with xrepo info <name>.
add_requires("mysql", {optional = true}) -- build continues if missing
add_requires("zlib", {system = true}) -- only use the system copy
add_requires("zlib", {system = false}) -- force xrepo to build it
if is_plat("linux") then
add_requires("libuuid")
end
add_requires("directxtk", {plat = "windows"})
add_repositories("my-repo https://github.com/me/my-xmake-repo.git")
add_requires("mypkg")
xrepo search fmt
xrepo info fmt
xrepo install "fmt 10.2.1"
xrepo env -b fmt bash # shell with fmt on PATH/PKG_CONFIG_PATH
xmake require --force fmtxmake require --cleanxmake require --info fmtxmake-optionsxmake-toolchains