-
Notifications
You must be signed in to change notification settings - Fork 0
Build From Source
Jfleezy edited this page May 2, 2026
·
5 revisions
The Windows stable app remains the WPF release line. This Wiki does not change the Windows source path, build path, runtime bootstrap, tests, or release process.
Recommended build:
.\scripts\Build-FramePlayer.ps1Direct build when the runtime is already staged:
.\scripts\Ensure-DevRuntime.ps1
.\scripts\Ensure-DevExportTools.ps1
.\scripts\Ensure-DevExportRuntime.ps1
dotnet build .\FramePlayer.csproj -c Release -p:Platform=x64Stage the pinned macOS FFmpeg runtime under Runtime/macos/osx-arm64/ffmpeg, then run:
dotnet build src/FramePlayer.Mac/FramePlayer.Mac.csproj -c Release
dotnet test tests/FramePlayer.Mac.Tests/FramePlayer.Mac.Tests.csproj -c Release --filter "Category!=ReleaseCandidate"
FRAMEPLAYER_MAC_CORPUS="Video Test Files" script/validate_macos_release_candidate.sh --corpus "Video Test Files"Package a local signed release candidate:
script/package_macos_release.sh --sign
codesign --verify --deep --verbose=2 "dist/Frame Player.app"Developer ID notarization is documented in docs/macos-preview-release.md.
FFmpeg playback and export runtimes are pinned. Runtime binaries are staged locally and are not committed unless a later release explicitly changes that policy.