How do I install the Xmake Dlang skill?

Run npx skillmds@latest add xmake-io/xmake-dlang in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Xmake Dlang safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Xmake Dlang?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Xmake Dlang free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Xmake Dlang?

xmake-io (@xmake-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Xmake Dlang by xmake-io — Agent Skill

Name: Xmake Dlang
Rating: 4.666666666666667 (3 reviews)
Author: xmake-io

File contents

Building D (dlang) with Xmake

D has three main compilers (DMD, LDC, GDC); xmake drives all of them through a unified target() API and supports DUB for package dependencies.

1. Minimal project

xmake create -l dlang -t console hello
cd hello
xmake run

add_rules("mode.debug", "mode.release")

target("hello")
    set_kind("binary")
    add_files("src/*.d")

2. Target kinds

target("app")       set_kind("binary")
target("mylib")     set_kind("static")
target("mydyn")     set_kind("shared")

3. DUB dependencies (v2.3.6+)

add_requires("dub::vibe-d ~>0.9.5")
add_requires("dub::libasync")

target("app")
    set_kind("binary")
    add_files("src/*.d")
    add_packages("dub::vibe-d", "dub::libasync")

Known limitation: cascading transitive deps must be declared manually for now. Add every dep in the tree explicitly.

4. Compiler selection

xmake f --toolchain=dlang                    # DMD (default)
xmake f --toolchain=ldc
xmake f --toolchain=gdc

Or pin paths:

xmake f --toolchain=ldc --sdk=/opt/ldc-1.30

LDC is usually the best choice for release builds (LLVM backend, best optimization). DMD is fastest to compile with.

5. Flags

target("app")
    add_files("src/*.d")
    add_dcflags("-O", "-release")          -- passed to the D compiler
    add_ldflags("-Wl,--as-needed")

add_dcflags = D compiler flags. Each compiler has its own flag dialect — prefer portable ones or gate with if is_toolchain("ldc") then ... end.

6. Mixing D with C

target("app")
    set_kind("binary")
    add_files("src/main.d", "src/extern.c")    -- mix C and D in one target
    add_includedirs("include")

D can call C directly via extern (C) declarations on the D side. No bridging needed.

Pitfalls

Transitive DUB deps. You must add them manually until xmake's DUB integration is complete.
Compiler-specific flags leaking across toolchains. add_dcflags("-mattr=+avx2") works on LDC, fails on DMD. Gate with is_toolchain.
D shared libraries on Windows. DMD and LDC produce different import-library formats; stick to one per project on Windows.

When to branch out

Build modes → xmake-targets, xmake-build-optimization
Cross-compile → xmake-cross-compilation (LDC supports many targets)
Package management basics → xmake-packages

---name: xmake-dlangdescription: Use when building D projects with xmake — binary/library targets with `.d` sources, DUB package integration via `add_requires("dub::...")`, and selecting DMD / LDC / GDC compilers.---# Building D (dlang) with XmakeD has three main compilers (DMD, LDC, GDC); xmake drives all of them through a unified `target()` API and supports DUB for package dependencies.## 1. Minimal project```bashxmake create -l dlang -t console hellocd helloxmake run``````luaadd_rules("mode.debug", "mode.release")target("hello") set_kind("binary") add_files("src/*.d")```## 2. Target kinds```luatarget("app") set_kind("binary")target("mylib") set_kind("static")target("mydyn") set_kind("shared")```## 3. DUB dependencies (v2.3.6+)```luaadd_requires("dub::vibe-d ~>0.9.5")add_requires("dub::libasync")target("app") set_kind("binary") add_files("src/*.d") add_packages("dub::vibe-d", "dub::libasync")```Known limitation: cascading transitive deps must be declared manually for now. Add every dep in the tree explicitly.## 4. Compiler selection```bashxmake f --toolchain=dlang # DMD (default)xmake f --toolchain=ldcxmake f --toolchain=gdc```Or pin paths:```bashxmake f --toolchain=ldc --sdk=/opt/ldc-1.30```LDC is usually the best choice for release builds (LLVM backend, best optimization). DMD is fastest to compile with.## 5. Flags```luatarget("app") add_files("src/*.d") add_dcflags("-O", "-release") -- passed to the D compiler add_ldflags("-Wl,--as-needed")````add_dcflags` = D compiler flags. Each compiler has its own flag dialect — prefer portable ones or gate with `if is_toolchain("ldc") then ... end`.## 6. Mixing D with C```luatarget("app") set_kind("binary") add_files("src/main.d", "src/extern.c") -- mix C and D in one target add_includedirs("include")```D can call C directly via `extern (C)` declarations on the D side. No bridging needed.## Pitfalls- **Transitive DUB deps.** You must add them manually until xmake's DUB integration is complete.- **Compiler-specific flags leaking across toolchains.** `add_dcflags("-mattr=+avx2")` works on LDC, fails on DMD. Gate with `is_toolchain`.- **D shared libraries on Windows.** DMD and LDC produce different import-library formats; stick to one per project on Windows.## When to branch out- Build modes → `xmake-targets`, `xmake-build-optimization`- Cross-compile → `xmake-cross-compilation` (LDC supports many targets)- Package management basics → `xmake-packages`

Frequently asked questions

Xmake Dlang