# mmozeiko/build-angle architecture

> Architecture diagram of the GitHub repository mmozeiko/build-angle, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-05-17). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/mmozeiko/build-angle
- Repository: https://github.com/mmozeiko/build-angle

## Overview

1. This repository is not an application codebase; it is a build-and-release automation repo for ANGLE, the OpenGL ES implementation, targeting 64-bit Windows.

2. The two functional parts are:
   - a GitHub Actions workflow under `.github/workflows/build-angle.yml`
   - a local build entrypoint, `build.cmd`

3. The workflow is the main automation subsystem. Based on the README, it runs a weekly build, producing binary artifacts for Windows x64 and Windows arm64.

4. The release boundary is important: the build output is packaged as a ZIP archive and published to the GitHub Releases page, where users download the “latest release” binary build.

5. `build.cmd` is the local build boundary. It is the script a developer runs to reproduce the CI build on a machine, assuming the required dependencies are installed. The README explicitly points to the top of that file for prerequisites.

6. The repo does not appear to contain ANGLE source code itself; it is a wrapper around fetching/building ANGLE and packaging the result. That means most of the real build complexity lives in the script and workflow, not in checked-in library code.

7. The external dependency model is simple but central:
   - GitHub Actions provides scheduled CI
   - GitHub Releases is the artifact distribution channel
   - ANGLE is the upstream project being built

8. Architecture-wise, the data flow is:
   source/build environment → `build.cmd` or GitHub Actions workflow → compiled Windows binaries → ZIP archive → GitHub Release download page.

9. Platform targeting is a key constraint in the design. The repo is specifically tuned for 64-bit Windows outputs, with separate x64 and arm64 builds, so the pipeline must handle both architectures in its build/package steps.

10. For an architecture diagram, the repo can be represented as a small automation system with three nodes: scheduled CI, local reproducible build script, and release artifact publishing. There are no additional subsystems visible from the file tree.

Main entry points: [`.github/workflows/build-angle.yml`](https://github.com/mmozeiko/build-angle/blob/main/.github/workflows/build-angle.yml) (Weekly build), [`build.cmd`](https://github.com/mmozeiko/build-angle/blob/main/build.cmd) (Build script)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_repo["Repo automation"]
  node_workflow["Weekly build<br/>GitHub Actions workflow<br/>[build-angle.yml]"]
  node_local_build["Build script<br/>Windows batch entrypoint<br/>[build.cmd]"]
end

subgraph group_external["External systems"]
  node_angle["ANGLE<br/>upstream project"]
  node_ci(("GitHub Actions<br/>CI scheduler"))
  node_release["GitHub Release<br/>artifact distribution"]
  node_win_x64{{"Win x64<br/>target architecture"}}
  node_win_arm64{{"Win arm64<br/>target architecture"}}
  node_zip["ZIP archive<br/>packaged artifact"]
end

node_ci -->|"schedules"| node_workflow
node_workflow -->|"builds"| node_angle
node_local_build -->|"builds"| node_angle
node_workflow -->|"targets"| node_win_x64
node_workflow -->|"targets"| node_win_arm64
node_workflow -->|"packages"| node_zip
node_local_build -.->|"packages"| node_zip
node_zip -->|"publishes"| node_release
node_release -->|"distributes"| node_workflow
node_local_build -.->|"mirrors"| node_workflow

click node_workflow "https://github.com/mmozeiko/build-angle/blob/main/.github/workflows/build-angle.yml"
click node_local_build "https://github.com/mmozeiko/build-angle/blob/main/build.cmd"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_workflow,node_local_build toneBlue
class node_angle,node_ci,node_release,node_win_x64,node_win_arm64,node_zip toneAmber
```

## Components

### Repo automation

Checked-in automation entrypoints that reproduce and publish ANGLE Windows builds.

- [Weekly build](https://github.com/mmozeiko/build-angle/blob/main/.github/workflows/build-angle.yml): GitHub Actions workflow · Scheduled CI pipeline that builds ANGLE for Windows x64 and arm64, packages ZIP artifacts, and publishes releases. · `.github/workflows/build-angle.yml`
- [Build script](https://github.com/mmozeiko/build-angle/blob/main/build.cmd): Windows batch entrypoint · Local reproducible build entrypoint for developers with the required dependencies installed. · `build.cmd`

### External systems

Upstream source, CI runtime, and release distribution surfaces.

- **ANGLE**: upstream project · External OpenGL ES implementation fetched and built by the automation.
- **GitHub Actions**: CI scheduler · Runs the weekly automated build workflow.
- **GitHub Release**: artifact distribution · Publishes ZIP archives for download as the latest binary release.
- **Win x64**: target architecture · Primary 64-bit Windows build target.
- **Win arm64**: target architecture · Secondary 64-bit Windows build target.
- **ZIP archive**: packaged artifact · Compressed build output produced by the pipeline before release publishing.

## Connections

- GitHub Actions → Weekly build: schedules · Triggers the weekly build workflow.
- Weekly build → ANGLE: builds · Fetches and builds the upstream ANGLE project.
- Build script → ANGLE: builds · Reproduces the same ANGLE build locally.
- Weekly build → Win x64: targets · Produces Windows x64 binaries.
- Weekly build → Win arm64: targets · Produces Windows arm64 binaries.
- Weekly build → ZIP archive: packages · Bundles build outputs into ZIP archives.
- Build script → ZIP archive: packages · Can reproduce the packaged build output locally.
- ZIP archive → GitHub Release: publishes · Uploads artifacts to GitHub Releases.
- GitHub Release → Weekly build: distributes · Release page exposes the latest CI-produced binary build.
- Build script → Weekly build: mirrors · Local script mirrors the CI build entrypoint and prerequisites.
