-
Notifications
You must be signed in to change notification settings - Fork 2.5k
ccextractor: update to 0.96.4 #58345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
674ffcc to
e68d167
Compare
e68d167 to
924cf95
Compare
|
ccextractor cannot be built without gpac now, but the latest release 2.4.0 is from april 2024. So with respect to the upcoming ffmpeg 8 update I used the latest snapshot instead of the release, because there have been quite some code changes with respect to ffmpeg which make patching 2.4.0 to support ffmpeg 8 troublesome with the potential for unwanted side effects. I have runtime tested ccextractor plus gpac-2.4.0.20251230 with ffmpeg 6 on x86_64 and aarch64 and with ffmpeg 8 on aarch64, working great, no problems found. |
|
all packages should be on stable releases. if it's infeasible, petition the upstream for a new release or keep ccextractor at an older release |
|
or alternatively, use an older ffmpeg for now |
924cf95 to
e663e19
Compare
|
@classabbyamp I switched this PR back to the stable gpac release. Somehow I was under the assumption that ffmpeg8 will replace ffmpeg6, but 6 will still be there and so we can keep ccextractor at that version, as you suggested. :) But I will also inquire gpac upstream if a new release is possible. However, they write here https://gpac.io/downloads/gpac-nightly-builds/:
They also have tags per abi version. Don’t know if this would be a proper alternative in case no release happens. |
|
would it make sense to split this into |
e663e19 to
06069be
Compare
06069be to
31165e3
Compare
|
Debian does the same and goes even further putting |
Testing the changes
Tested on x86_64 and aarch64:
New package
Local build testing
Fails to build on 32 bit targets, reported upstream and is fixed in upcoming 0.96.4.Edit: all builds succeed now.