Repository navigation
build: build with ffmpeg-build - #60
Merged
Merged
Conversation
ffmpeg-build.yml holds the 120 builds (FFmpeg 8 and 9, 15 platforms, four licenses) and ffmpeg.lock their versions; the CI, release and lock-update workflows call ffmpeg-build's reusable workflows. The build scripts, the version ledger, Renovate and the generated matrix docs go. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
THIRD-PARTY-NOTICES.txt replaces legal/; gplv2 builds gain SRT/RIST encryption (mbedTLS under its GPL-2.0-or-later option); v2 Windows and Android Whisper runs on the GPU through the system's Vulkan library. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lock updates are opened as devenvy-bot, so they start CI and code scanning, and merge once the result check passes; Dependabot's action bumps merge the same way; a new FFmpeg major is reported. Permissions are granted per job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s to v0.0.2 NVENC needs driver 570+ on SDK 13.0 and 610+ on 13.1, which the last driver branch for GTX 900/10-series cards never reaches (#54). The engine's reusable workflows are pinned by commit, as the org's code scanning expects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 14, 2026
chore(actions): Bump renovatebot/github-action from 46.3.6 to 46.3.7 in the github-actions group
#59
Closed
Closed
GnuTLS's system priority file is /etc/gnutls/config rather than a path inside the build's deps folder, which the maccatalyst gplv2 builds' release check rejected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ryan-morris
force-pushed
the
chore/ffmpeg-build
branch
from
October 14, 2026 23:52
6fff813 to
493bd06
Compare
The builds install the engine the lock names, so the GnuTLS fix in 0.0.3 needs the lock to name it too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…orkflow A pull request now runs ffmpeg-build's check.yml (is ffmpeg-build.yml valid, does ffmpeg.lock cover it, can every target be planned) in a minute instead of building every target; the daily release builds and tests them all before it publishes. codeql.yml scans the workflows on every pull request, on main and weekly, in place of the default setup. ffmpeg-build's workflows move to v0.0.5; workflow names are capitalised like the other repositories'. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
This repository stops building FFmpeg with its own scripts and builds it with ffmpeg-build instead. The same 120 builds are defined in
ffmpeg-build.yml, versions are locked inffmpeg.lock, and small workflows call ffmpeg-build's reusable workflows (pinned by commit):ci.yml: checksffmpeg-build.ymlandffmpeg.lock(valid, every target can be planned) in a minute, building nothing; merges the lock updates and Dependabot's PRs onceresultpasses.codeql.yml: CodeQL on the workflows, on every PR, onmainand weekly (security-and-quality queries).release.yml: the daily release of whatever changed. It builds and tests every target of a release before publishing it.update-lock.yml: the daily lock update (new library versions, FFmpeg point releases, new ffmpeg-build versions), opened as devenvy-bot so it gets CI and code scanning like any PR.Removed:
scripts/(the bash build system),deps.json, Renovate, the generated matrix docs, the old CodeQL workflow and config (C/C++ and the.build/exclusion no longer apply; the newcodeql.ymlscans the workflows),DEVELOPMENT.mdandSOURCE_OFFER.txt. The docs are a README and one usage page.Same as today
All 120 targets (FFmpeg 8 and 9 × 15 platforms × 4 licenses) were built and tested with this engine before this PR: every Linux, Windows and Android build, and every kind of Apple build. Spot comparisons with the published 9.0.2.3 archives (linux-x64-gplv3, linux-musl-x64-lgplv2) found the same files, configure flags, registered components, sonames and linking. Asset names, the iOS bundle layout,
SHA256SUMSand the 4-part tags are unchanged; the next releases are 8.1.3.4 and 9.0.2.4.Carried over: the NVIDIA headers hold on SDK 13.0 (#54, as
pin: { nvenc: '13.0' }); the mbedTLS 3.x hold (#18, now in ffmpeg-build's recipe); Vulkan on the Apple v3 builds through MoltenVK; win-x64 debug symbols (#20) as a release asset.Changes on purpose
legal/becomes oneTHIRD-PARTY-NOTICES.txtat each archive's root (devenvy/ffmpeg-dotnet is updated to match before its next release).manifest.yml(what each build is made of) andffmpeg-<version>-sources.tar.gz.Before merging
mainruleset should requireresult(the old branch protection'sbuild/test/Analyze (c-cpp)/shellcheckchecks no longer exist).🤖 Generated with Claude Code