mirror of
https://github.com/CCExtractor/ccextractor.git
synced 2026-02-16 21:23:35 +00:00
[PR #1454] [CLOSED] [WIP] attempt compatibility with ffmpeg #2192
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/CCExtractor/ccextractor/pull/1454
Author: @shashwat1002
Created: 9/26/2022
Status: ❌ Closed
Base:
master← Head:ffmpeg5_compat📝 Commits (4)
e7e3bc3add lib_hardsubx_ctx struct to mod.rs of hardsubxdf0b9c5take care of external dependencies and general bindings25620ddmake code_ctx of the AVCodecParameters type of ffmpeg for ffmpeg5 comatibility9cc7b3amain code and hide hardsubx_process_data's C version. The linker fucks up rn📊 Changes
8 files changed (+503 additions, -11 deletions)
View changed files
📝
src/lib_ccx/hardsubx.c(+2 -0)📝
src/rust/Cargo.lock(+58 -4)📝
src/rust/Cargo.toml(+5 -2)📝
src/rust/build.rs(+15 -4)➕
src/rust/src/hardsubx/main.rs(+256 -0)📝
src/rust/src/hardsubx/mod.rs(+163 -0)📝
src/rust/src/lib.rs(+1 -1)📝
src/rust/wrapper.h(+3 -0)📄 Description
This is the work for compatibility with ffmpeg. The current problem is that certain hardsubx functions on the C side are not discoverable by the linker when Rust code tries to call them.
I think eventually I will have to close this PR and PR #1446 and have the common changes in a third PR that'll be easier than dealing with the merge conflicts.
Because this has taken far too much time, I'll roll back to ffmpeg 4 for now and continue porting. I really wanted to deal with this before.
PS: Pardon the impolite commit language. I plan to clean up the commit history
cc: @PunitLodha @cfsmp3
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.