dexoron/dcr
1
1
Fork 0
mirror of https://github.com/dexoron/dcr.git synced 2026-10-21 17:29:36 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
12d1bc51118fea17aa97ee422ec1d1fea38f8231
dcr/docs/commands/dcr-build.md
Dexoron 7969209eae Added: 
- `build.kind = "efi"` — UEFI PE32+ executable support. Links with `-shared -nostdlib -Wl,-dll -Wl,--subsystem,10`, output via `efi_path()` with `.efi` extension, rejected by `dcr run`.
- `build.kind = "elf"` — bare-metal ELF executable support. Uses `elf_path()` output path, rejected by `dcr run`, no extra linker flags.

Fixed:

- `dcr run` with `--target` or `build.target` now correctly finds the binary in the arch-specific target directory.
- `dcr run` checks profile-specific `build.{profile}.kind` before rejecting library builds (previously only checked `build.kind`).
- `dcr clean` now reads `build.target` from `dcr.toml` when no `--target` flag is given.
- Linux: target directory is now consistent — `target/<arch>-unknown-linux-gnu/<profile>/` (no stale `target/<profile>/`).
- `dcr.lock` is now populated with all resolved dependencies (registry, path, git) instead of being always empty.
- Git dependencies are now properly recognized and recorded in `dcr.lock`.
- `is_registry_dep` correctly identifies version-based registry dependency tables (`{ version = "..." }`) and rejects tables with unknown keys.
- `dcr test` accepts `--debug`/`--release` flags (defaults to `debug` profile instead of always `release`).
- Build fingerprint cache (`build_cache_path`) now includes `target_dir` — different targets no longer share a single cache entry.
- `object_path` no longer hardcodes the `src/` prefix — works correctly with custom `build.roots` (e.g. `roots = ["lib"]`).
- `dcr update` now generates `.exe` candidates for all Windows targets, not just `x86_64-pc-windows-msvc`.
- Compiler existence is verified before starting the build (clear error if compiler is not found in PATH).
- Consolidated duplicate `OUTPUT_MUTEX` definitions — MSVC backend now uses the shared mutex from `common.rs`.
- Registry cache root directory is created if missing (prevents cryptic errors when `~/.dcr/` does not exist).
2026-05-26 16:38:23 +08:00

3.2 KiB
Raw Blame History

dcr build

Builds the project in debug or release profile.

Usage

dcr build
dcr build --debug
dcr build --release
dcr build --target linux --release
dcr build --release --force
dcr build --debug --clean

What build does

  1. Checks that dcr.toml exists and is valid.
  2. Reads build settings from [build].
  3. Resolves path dependencies from [dependencies].
  4. Creates required output directories.
  5. Recursively compiles sources from src/.
  6. Links final artifact (binary or library).

Config values used

  • package.name
  • build.filename
  • build.extension
  • build.compiler
  • build.language
  • build.standard
  • build.kind
  • build.target
  • build.platform
  • build.cflags
  • build.ldflags
  • build.ldscript
  • build.debug / build.release
  • build.exclude
  • build.include
  • build.pkg_config
  • build.steps
  • build.post_steps
  • build.generated
  • build.expect
  • build.clean

Source selection

  • language = "c" -> *.c
  • language = "c++" | "cpp" | "cxx" -> *.cpp, *.cxx, *.cc
  • language = "asm" -> *.s, *.S, *.asm
  • Mixed languages are supported with arrays, for example language = ["c", "asm"].
  • By default sources are searched in src/; use build.roots and build.src_disable to override.

Notes

  • Profile flag (--debug / --release) can appear in any argument position (duplicates are rejected).
  • Unknown profile flags return an error.
  • --target <triple> builds for specified target (short names: linux, macos, windows).
  • --verbose prints the compiler/linker command lines to stderr (also works via DCR_DEBUG env var).
  • If no --target, builds for build.targets or native.
  • Incremental rebuild checks source/object mtime and tracked header dependencies.
  • --force skips build cache checks and recompiles.
  • --clean removes target/<profile> and build.clean paths before building.
  • build.filename + build.extension allow full control over the final artifact name (e.g. KERNEL.BIN instead of using package.name). When build.kind = "efi", the output is a PE32+ executable with .efi extension.
  • build.kind = "efi" links with -shared -nostdlib -Wl,-dll -Wl,--subsystem,10 for UEFI PE32+ format. Use build.filename and build.extension for full control over the artifact name.
  • build.kind = "elf" produces a bare-metal ELF executable. Linking flags are user-controlled via build.ldflags (no PIE/CRT defaults are added).
  • Default GCC/Clang profile flags: debug -> -O0 -g -Wall -Wextra -fno-omit-frame-pointer -DDCR_DEBUG, release -> -O3 -DNDEBUG. These defaults are not applied for bare-metal targets (e.g. aarch64-none-elf, targets containing none / -elf / eabi).
  • For language = "asm" with compiler = "as"/"gas", use .s files (no preprocessing). For .S, use gcc or clang.
  • In workspace root, dcr build builds all members in dependency order.
  • build.exclude removes paths from source/header collection; build.include re-allows matching paths and has priority over exclude.
  • build.steps run before compilation; build.post_steps run after linking.
  • build.generated is cleaned when build.steps need to rerun; build.expect is verified after post-steps.