Skip to content
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

nv-codec-headers: update to 11.1.5.3. #51138

Closed
wants to merge 1 commit into from

Conversation

dataCobra
Copy link
Contributor

Testing the changes

  • I tested the changes in this PR: briefly

Local build testing

  • I built this PR locally for my native architecture, (x86_64-musl)
  • I built this PR locally for these architectures (if supported. mark crossbuilds):
    • x86_64-musl
    • i686

#50982

@zlice could you test ffmpeg with this version? Since it's still 11.x everything should be fine.

@zlice
Copy link
Contributor

zlice commented Jul 7, 2024

I'm still using the 12 version we both had a while back #44781 - works for ffmpeg 4 and 6. Rolled into #51132. Sounded like the best way to slowly upgrade to 6 and not cause a headache for everyone. iirc 6 needs nv-codec 12+

update - 6 compiles fine with this 11 version. I don't use nvidia so either version should be fine 👍

@dataCobra
Copy link
Contributor Author

I'll close this in favor of version 12.x.

@zlice could you maybe test which of the latest 12.x versions is still working for Void and your PR?

nv-codec-headers is one of the packages that has pretty good changes with every version.

@dataCobra dataCobra closed this Jul 8, 2024
@dataCobra dataCobra deleted the nv-codec-headers branch July 8, 2024 14:55
@zlice
Copy link
Contributor

zlice commented Jul 10, 2024

fwiw 12.0.16.1 is the latest version that works with ffmpeg 4

i can see there being another nv-codec package when things all move over except the few ffmpeg stragglers. but that will be a while

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.

2 participants