# Build Scripts in denoland/celld: What the Source Code Reveals > Discover if denoland/celld uses build scripts. Explore how it leverages Cargo's native build pipeline, bypassing custom build.rs files, Makefiles, and shell scripts for efficient development. - Repository: [Deno/celld](https://github.com/denoland/celld) - Tags: internals - Published: 2026-09-05 --- **No, the denoland/celld repository does not contain any build scripts.** The project relies entirely on Cargo's native build pipeline without custom [`build.rs`](https://github.com/denoland/celld/blob/main/build.rs) files, Makefiles, or shell scripts. The **celld** project is a pure-Rust workspace developed by Deno. It's distributed across multiple crates, where Cargo natively handles all compilation steps. Any developer familiar with Rust will recognize this as a standard, clean setup that doesn't require manual build orchestration. ## How Celld Builds Without Custom Scripts Cargo's default behavior is sufficient for celld's architecture. The repository root contains [`Cargo.toml`](https://github.com/denoland/celld/blob/main/Cargo.toml), which declares workspace members and dependencies. Cargo reads this file directly and manages the entire compilation flow. ### What Files Control the Build Process Instead of build scripts, celld uses these key files: - **[`Cargo.toml`](https://github.com/denoland/celld/blob/main/Cargo.toml)** — Workspace configuration with crate metadata and dependencies - **`Dockerfile`** — Container image for running the compiled binary (not a build script) - **[`.github/workflows/release.yml`](https://github.com/denoland/celld/blob/main/.github/workflows/release.yml)** — CI pipeline that invokes `cargo build` and `cargo test` No [`build.rs`](https://github.com/denoland/celld/blob/main/build.rs) files exist anywhere in the repository. A search for `**/build.rs` returns zero matches. Similarly, no `Makefile` or shell scripts (`**/*.sh`) are present. ## The Cargo.toml Workspace Structure The [`Cargo.toml`](https://github.com/denoland/celld/blob/main/Cargo.toml) at the repository root defines a **Cargo workspace**. This is the authoritative source for how the project builds: ```toml [workspace] members = ["crates/*"] ``` This configuration tells Cargo to treat every subdirectory under `crates/` as its own crate. The workspace structure typically includes: - `crates/logic/` — Core business logic - `crates/ltx/` — Likely transaction or protocol handling - `crates/celld/` — Main binary crate Since no `[build-dependencies]` section references custom build tooling, and no individual [`Cargo.toml`](https://github.com/denoland/celld/blob/main/Cargo.toml) in member crates specifies a `build = "..."` key, Cargo proceeds with its standard compilation pipeline. ## CI Build Configuration vs. Build Scripts The [`.github/workflows/release.yml`](https://github.com/denoland/celld/blob/main/.github/workflows/release.yml) file automates builds across platforms, but this is **CI configuration**, not a project-internal build script. According to the celld source code, this workflow: 1. Checks out the repository 2. Installs the Rust toolchain 3. Runs `cargo build --release` 4. Runs `cargo test` 5. Produces release artifacts This automation doesn't replace or supplement Cargo's build process—it simply invokes it in a controlled environment. ## Building Celld from Source Without any build scripts, compiling celld is straightforward. Use these commands: ```bash # Clone the repository git clone https://github.com/denoland/celld.git cd celld # Build all crates in the workspace (debug mode) cargo build # Build optimized release binaries cargo build --release # Run the test suite cargo test ``` Cargo handles dependency resolution, parallel compilation of workspace members, and final linking without intervention. ## Why No Build Scripts Are Needed The absence of [`build.rs`](https://github.com/denoland/celld/blob/main/build.rs) indicates celld doesn't require: - **Code generation** at compile time (no protobuf, no template engines) - **Native library linking** (no C dependencies requiring `cc` crate) - **Environment probing** (no feature detection for OS capabilities) This is consistent with modern Rust projects that operate entirely within Cargo's ecosystem. The `Dockerfile` present in the repository serves deployment purposes—it copies a pre-built binary into a container, rather than compiling inside it. ## Summary - **No [`build.rs`](https://github.com/denoland/celld/blob/main/build.rs) files** exist in denoland/celld (`**/build.rs` returns zero matches) - **No Makefile or shell scripts** handle compilation - **Cargo.toml** alone defines the workspace and build configuration - **Standard `cargo build`** commands compile all crates successfully - **CI automation** in [`.github/workflows/release.yml`](https://github.com/denoland/celld/blob/main/.github/workflows/release.yml) invokes Cargo directly ## Frequently Asked Questions ### Does celld use a custom build script for code generation? No. The repository contains no [`build.rs`](https://github.com/denoland/celld/blob/main/build.rs) files, which means no custom code generation occurs during compilation. All source files are written manually and checked into version control. ### Can I build celld without Cargo? No. Celld is a Rust project with no alternative build system configured. You must use Cargo, which is distributed with the Rust toolchain. There is no Makefile or CMake configuration present. ### What does the Dockerfile in celld do? The `Dockerfile` provides a container image for running the already-compiled celld binary. It does not compile the source code; it expects a binary built externally via `cargo build --release` to be copied into the image. ### How does celld handle cross-platform builds? Cross-platform builds are handled by GitHub Actions in [`.github/workflows/release.yml`](https://github.com/denoland/celld/blob/main/.github/workflows/release.yml). The CI matrix builds for multiple targets using standard Cargo commands. No platform-specific build logic exists in the repository itself.