Files
Velix-MPV-Core/UPSTREAM.md
T

49 lines
2.4 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Upstream 基线
| 项目 | 值 |
|---|---|
| MPV Repository | `https://github.com/mpv-player/mpv.git` |
| MPV Current Commit | `182fa6ca49f455cadb884858f386e2f00540aeb7` |
| Commit Date | 2026-08-26 |
| MPV Version / Tag | `MPV_VERSION=0.41.0-UNKNOWN`;`git describe=git-release-292-g182fa6ca49`;HEAD 无 tag |
| Fork Date | 2026-08-28 |
| Development Branch | `harmony-port` |
| HarmonyOS Target | HarmonyOS NEXT / OpenHarmony Native API 24 |
| HarmonyOS SDK | DevEco Studio 内置 OpenHarmony SDK `6.1.1.125`,API 24 |
| Target Architecture | `arm64-v8a` / `aarch64-linux-ohos` |
| Compiler | OHOS Clang `15.0.4` (`99548401bd80576251755b185ab95945e5fe7884`) |
| Build System | MPV Meson `>=1.3.0` + Ninja;依赖使用各自原生构建系统 |
Velix-MPV-Core 是基于 MPV upstream Git 历史维护的独立派生仓库,不是 GitHub Fork。仓库完整保留 upstream history、基线 commit、MPV 版权与许可证文件,并持续保留 `upstream` remote。
## FFmpeg 基线
| 项目 | 值 |
|---|---|
| Repository | `https://git.ffmpeg.org/ffmpeg.git` |
| Commit | `3acec0a1af2dda0a0838689b8b8649e7deb080a0` |
| Commit Date | 2026-08-28 |
| git describe | `3acec0a`(该 commit 无可达 tag) |
| License Mode | LGPL-2.1-or-later;`CONFIG_GPL=0`、`CONFIG_VERSION3=0`、`CONFIG_NONFREE=0` |
| Build | 静态 PIC;禁用 programs、docs、debug、avdevice 与 autodetect |
| Enabled | network、OpenSSL、zlib、OHCodec |
| OHCodec | `AV_HWDEVICE_TYPE_OHCODEC`、`AV_PIX_FMT_OHCODEC`、H.264/HEVC OH decoder/encoder 已编译 |
FFmpeg configure 参数由 `scripts/build-ffmpeg-ohos.sh` 固定。当前不创建 Velix FFmpeg fork;只有 upstream 出现需要长期维护的真实 blocker 时才重新评估。
## 远程状态
- `upstream` 已指向 MPV 官方仓库。
- `origin` 已指向独立仓库 `https://git.leee.xin/leeexin/Velix-MPV-Core.git`。
- 远程默认分支为 `harmony-port`,同时保留与官方基线一致的 `master` 和 89 个官方标签。
```sh
git fetch upstream
git fetch origin
git log --oneline --decorate harmony-port..upstream/master
git diff harmony-port...upstream/master
git range-diff <old-upstream>..harmony-port upstream/master..<rebased-candidate>
```
基线更新必须先检查 `git log`、`git diff` 和适用的 `git range-diff`,再评估使用 merge 或 rebase,并同步更新本文件。禁止直接强制覆盖 `harmony-port`。