Skip to content

build(deps)!: migrate FFmpeg dependencies to CPM - #843

Merged
ReenigneArcher merged 3 commits into
masterfrom
codex/cpm-dependencies
Nov 20, 2026
Merged

ReenigneArcher merged 3 commits into
masterfrom
codex/cpm-dependencies

Conversation

@ReenigneArcher

@ReenigneArcher ReenigneArcher commented Nov 20, 2026 •

Copy link
Copy Markdown
Member

Description

Fetch FFmpeg and its six companion dependencies through CPM at their existing revisions. CPM applies the patches during source population, and the build uses its existing codec targets and packaging rules. Remove the patch-only CMake switches and recursive submodule checkout. Clear inherited Make jobserver flags from FFmpeg's nested build and install to fix the macOS ARM64 CI failure.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Testing

Local validation covered clean configure and reconfigure for FFmpeg, Opus, and x265, a minimal Linux FFmpeg build and install, a Linux Opus build, and Windows x264 and x265 multilib builds during development.

The PR CI run passed all ten platform builds and package checks. Each archive matches its counterpart from the base-commit run across all 3,743 paths, entry types, link targets, and permissions.

SHA-256 differs for 637 file payloads. Differences include compiled outputs, generated version metadata, a CMake export policy version, and Windows text line endings.

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

  • AI tools were used while preparing this PR

@ReenigneArcher
ReenigneArcher marked this pull request as ready for review November 20, 2026 17:32
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant