If you are just decoding video (not encoding), consider dav1d for AV1 or ffmpeg with --enable-libvpx --disable-everything . But that is a story for another day.
In the world of open-source multimedia, libvpx is a titan. Developed by Google, it is the reference implementation for the VP8 and VP9 video codecs—the technologies that power YouTube, WebM, and billions of browser-based video calls. bloat libvpx
--disable-vp8-encoder --disable-vp9-decoder When cross-compiling, specify exactly the architecture: If you are just decoding video (not encoding),
Until then, if your binary is too fat, remember: It's not the codec's fault. You just compiled the reference implementation for the reference machine. Trim the flags, target your silicon, and libvpx will slim down. Developed by Google, it is the reference implementation
./configure --size-limit=640x480 --enable-small --enable-small trades speed for size. It disables loopfilter optimizations and reduces memory overhead. For embedded decoding, this is often invisible to the user. Yes and no.
But in recent years, a quiet grumble has emerged from embedded systems engineers, Linux distribution maintainers, and build-from-source enthusiasts. That grumble has a name: What is "Bloat libvpx"? To the uninitiated, "bloat" might sound like an insult. In this context, it’s a technical observation. "Bloat libvpx" refers to the phenomenon where the standard compilation of the library produces a binary that is significantly larger, slower to compile, or more resource-hungry than necessary for a given use case.