How jens-duttke/oku3d-ffmpeg works
This repository builds and packages customized FFmpeg binaries for multiple operating systems, architectures, and licensing variants. The documented user workflow selects a target, variant, and optional addins, builds a Docker image, then builds FFmpeg and obtains a ZIP artifact. Package build definitions and target-specific toolchain images support that workflow; scheduled builds and releases are also documented. The Oku3D directory contains specialized build-surface and GPL checks. Build-script internals and automation wiring were not sampled, so those connections are limited to README evidence.
Main entry points: build.sh FFmpeg builder · makeimage.sh Image builder · workflows Scheduled builds · surface.c Surface probe
Components 14
Build workflow
- Image builder
makeimage.sh - FFmpeg builder
build.sh - ZIP artifact
- Scheduled builds
.github/workflows - Automated releases
.github/workflows
Build configuration
- Build variants
variants - Build addins
addins - Dependency recipes
scripts.d
Platform toolchains
- Base image
images/base - Target toolchains
images
Oku3D checks
- Surface probe
oku3d/surface.c - Surface comparison
oku3d/compare_surface.py - GPL scanner
oku3d/gpl_scan.py
Other components
- Builder
Connections 12
- Builder → Image builder: selects target
README.md - Builder → FFmpeg builder: selects variant
README.md - Image builder → FFmpeg builder: prepares image
README.md - FFmpeg builder → ZIP artifact: produces ZIP
README.md - FFmpeg builder → Build variants: uses variant
README.md - FFmpeg builder → Build addins: accepts addins
README.md - FFmpeg builder → Dependency recipes: builds packages
README.md - Image builder → Base image: builds image
- Image builder → Target toolchains: selects toolchain
- Scheduled builds → FFmpeg builder: runs builds
README.md - Scheduled builds → Automated releases: releases on success
README.md - Surface probe → Surface comparison: supplies surface
oku3d/compare_surface.py