# Introduction

DCR (Dexoron Cargo Realization) is a Cargo-style CLI for C/C++ projects.

Current DCR focuses on a simple, predictable workflow:

* create or initialize a project (`dcr new`, `dcr init`)
* build with `debug` or `release` profiles (`dcr build`)
* run binaries (`dcr run`)
* clean artifacts (`dcr clean`)
* update the installed binary (`dcr --update`)

## What is implemented in this version

* Project configuration in `dcr.toml` with `[package]`, `[build]`, `[dependencies]`.
* Recursive source discovery in `src/`:
  * C: `*.c`
  * C++: `*.cpp`, `*.cxx`, `*.cc`
* Compiler selection from `dcr.toml` (`clang`, `gcc`, `cl`, `clang-cl`, etc.).
* ASM support via `language = "asm"` (GCC/Clang, NASM, GAS).
* Mixed language builds via `language = ["c", "asm"]` and similar combinations.
* Three build kinds:
  * `bin` (default)
  * `staticlib`
  * `sharedlib`
* Optional custom output directory via `build.target`.
* Optional `build.platform` to pass architecture hints (`-march` / `/arch`).
* Optional `build.exclude`/`build.include` for source/header selection.
* Optional `build.roots`/`build.src_disable` to replace the default `src/` root.
* Optional build steps with `build.steps` and `build.post_steps`.
* Optional `build.pkg_config` integration.
* Optional `build.clean` and `build.expect`.
* Optional `[run].cmd` to override run command.
* Workspace builds via `[workspace]` with per-project `dcr.toml`.
* Path dependencies with include/lib resolution and `dcr.lock` generation.

## Important behavior notes

* `dcr.toml` is required for `build`, `run`, and `clean`.
* `run` works only with `build.kind = "bin"`.
* Incremental rebuild tracks source file timestamps and header dependencies (rebuilds when either source or included headers change).
* Object files are always created under `target/<profile>/obj/`.

## Repository

* <https://github.com/dexoron/dcr>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dexoron-studio.gitbook.io/dcr/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.