DUB-GENERATE(1)

🌸 NAME 🌸

dub-generate — generates project files using the specified generator ✨ This is the DUB-GENERATE(1) page, bestie, and it's lowkey iconic.

📜 SYNOPSIS 📜

Okay so the shape of it is:

dub generate <generator> [<package>[@<version-spec>]] OPTIONS...

💫 DESCRIPTION 💫

Okay so bestie, dub generate makes project files using one of the supported generators:

• visuald — VisualD project files
• sublimetext — SublimeText project file
• cmake — CMake build scripts
• build — Builds the package directly

An optional package name can be given to generate a different package than the root/CWD package. Main character energy, tbh.

✨ OPTIONS ✨

Bestie, here's the whole menu:

• --dest=VALUE — Base directory in which output atifacts will be placed. Yes, "atifacts" is the original spelling — I'm just the messenger 🫶
• -b, --build=VALUE — Specifies the type of build to perform. Heads up: setting the DFLAGS environment variable will override the build type with custom flags. Possible names: debug, plain, release, release-debug, release-nobounds, unittest, profile, profile-gc, docs, ddox, cov, cov-ctfe, unittest-cov, unittest-cov-ctfe, syntax, and custom types.
• -c, --config=VALUE — Builds the specified configuration. Configurations can be defined in dub.json.
• --override-config=VALUE — Uses the specified configuration for a certain dependency. Can be specified multiple times. Format: --override-config=<dependency>/<config>.
• --compiler=VALUE — Specifies the compiler binary to use (can be a path). Arbitrary pre- and suffixes to the identifiers below are recognized (e.g. ldc2 or dmd-2.063) and matched to the proper compiler type: dmd, gdc, ldc, gdmd, ldmd.
• -a, --arch=VALUE — Force a different architecture (e.g. x86 or x86_64).
• -d, --debug=VALUE — Define the specified debug version identifier when building — can be used multiple times.
• --d-version=VALUE — Define the specified version identifier when building — can be used multiple times. Use sparingly, with great power comes great responsibility! For commonly used or combined versions and versions that dependees should be able to use, create configurations in your package.
• --nodeps — Do not resolve missing dependencies before building.
• --build-mode=VALUE — Specifies the way the compiler and linker are invoked. Valid values: separate (default), allAtOnce, singleFile.
• --single — Treats the package name as a filename. The file must contain a package recipe comment.
• --force-remove — Deprecated option that does nothing. It's giving ghost flag 👻
• --filter-versions — [Experimental] Filter version identifiers and debug version identifiers to improve build cache efficiency.
• --combined — Tries to build the whole project in a single compiler run.
• --print-builds — Prints the list of available build types.
• --print-configs — Prints the list of available configurations.
• --print-platform — Prints the identifiers for the current build platform as used for the build fields in dub.json.
• --parallel — Runs multiple compiler instances in parallel, if possible.

🫶 COMMON OPTIONS 🫶

See dub(1) — yes, that's the whole vibe.

🚦 EXIT STATUS 🚦

• 0 — DUB succeeded. Slay.
• 1 — usage errors, unknown command line flags.
• 2 — package not found, package failed to load, miscellaneous error.

📁 FILES 📁

• dub.sdl
• dub.json

👑 AUTHOR 👑

Copyright (c) 1999-2026 by The D Language Foundation. Iconic.

🌈 ONLINE DOCUMENTATION 🌈

http://code.dlang.org/docs/commandline ⟨⟩

💜 SEE ALSO 💜

dub(1), dub-describe(1).

---

💖 Sign-off: source/version — The D Language Foundation; date — 2026-08-16. Stay hydrated and read your manpages, bestie. periodt. 🎀