dexoron/dcr
1
1
Fork 0
mirror of https://github.com/dexoron/dcr.git synced 2026-10-21 14:08:30 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
e6788b4d7137c1cabf3c4e9af9938392d70ffc95
dcr/docs/dependencies-and-build/target-directory.md
Dexoron 865d8c52ff fix: split target into target (triple) and out_dir (output directory) 
build.target now holds the target triple (e.g. x86_64-unknown-linux-gnu)
build.out_dir is a custom output directory that overrides the default
target/<triple>/<profile> path.
2026-05-30 14:18:54 +08:00

1020 B
Raw Blame History

Target directory

By default, DCR writes final artifacts to target/<target>/<profile>/ (where <target> is native or target triple).

You can override this with build.out_dir:

[build]
out_dir = "./dist"

Behavior

  • Binary mode:
    • Linux/macOS: <out_dir>/<name>
    • Windows: <out_dir>/<name>.exe
  • Static library mode:
    • Linux/macOS: <out_dir>/lib<name>.a
    • Windows: <out_dir>/<name>.lib

Important detail

build.out_dir changes only the final artifact location. Object cache and dependency sync directories still use target/<target>/<profile>/....

Distinction from platform targets

  • build.out_dir — custom output directory path.
  • build.target / --target <triple> CLI flag — platform target for cross-compilation (e.g. x86_64-unknown-linux-gnu, or short name linux).
  • build.targets (array) — list of platform targets to build simultaneously.
  • [build.<target>] sections — target-specific config overrides (e.g. [build.linux]).