How zqinking/wrt_release works
This repository automates building device-specific OpenWrt-family firmware. The documented workflow selects a device and build mode, combines its build metadata and configuration, updates source and package feeds, applies customizations, builds (optionally in Docker), and collects firmware output. The README documents responsibilities and stages, but no source excerpts were provided, so the graph avoids claims about specific script-level calls.
Main entry points: build.sh Build entry · update.sh Source update · build_container.sh Container build · compilecfg Device metadata
Components 14
Build orchestration
- Build entry
build.sh - Source update
wrt_core/update.sh
Device configuration
- Device metadata
wrt_core/compilecfg - Device config
wrt_core/deconfig - Config fragments
wrt_core/deconfig/fragments
Source customization
- Feed adjustments
wrt_core/modules/feeds.sh - Package sync
wrt_core/modules/packages.sh - Build patches
wrt_core/patches
Build and output
- Container build
wrt_core/build_container.sh - Firmware build
wrt_core/update.sh - Firmware output
Other components
- Builder
- Firmware source
- Docker runtime
Connections 13
- Builder → Build entry: selects device
README.md - Build entry → Device metadata: reads build metadata
README.md - Build entry → Device config: combines configuration
README.md - Build entry → Config fragments: selects fragments
README.md - Build entry → Source update: runs update flow
README.md - Source update → Firmware source: pulls source
README.md - Source update → Feed adjustments: adjusts feeds
README.md - Source update → Package sync: syncs packages
README.md - Source update → Build patches: applies patches
README.md - Build entry → Container build: starts container build
README.md - Container build → Docker runtime: uses runtime
README.md - Build entry → Firmware build: runs full build
README.md - Build entry → Firmware output: collects firmware
README.md