-
Notifications
You must be signed in to change notification settings - Fork 1
libopus feature for ffmpeg #37
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The libopus
build definition must be in a separate port, see https://github.com/holepunchto/bare-ffmpeg/blob/main/cmake/ports/svt-av1/port.cmake for an example. It's fortunately built with CMake as well so the port should be trivial.
@kasperisager makes sense! Is there a way around recreating the equivalent of bare_arch for checking the arch? |
That shouldn't be necessary at all. What's the issue you're running into? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good % @kasperisager comment! :)
Ah, I see, I guess I was assuming because of this in the x264 port, which we could probably remove? bare-ffmpeg/cmake/ports/x264/port.cmake Lines 23 to 65 in 564d5b4
I got a little too into figuring out how the libopus build works with neon but I figured out the right option to make it build. Assuming the workflow jobs succeed I think this is probably good now! |
Narrator voice: "But not all the workflow jobs would succeed." Now they do! I got really into getting simd intrinsics working across platform/arch. Possibly too into it. |
Co-authored-by: Kasper Isager Dalsgarð <[email protected]>
Co-authored-by: Kasper Isager Dalsgarð <[email protected]>
Co-authored-by: Kasper Isager Dalsgarð <[email protected]>
Co-authored-by: Kasper Isager Dalsgarð <[email protected]>
No description provided.