--disable-vp8-encoder --disable-vp9-decoder When cross-compiling, specify exactly the architecture:
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
The problem isn't Google's code. The problem is that the open-source ecosystem has standardized on a as the default. We need better documentation for "embedded" or "minimal" profiles. The problem is that the open-source ecosystem has
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. That grumble has a name: What is "Bloat libvpx"
We aren't talking about malware. We are talking about feature creep .
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.
./configure --disable-runtime-cpu-detect --enable-static This tells the compiler: "Don't write the dispatcher. Just write the code for the CPU I am sitting on." This can cut binary size by 30-40%. Don't need VP8? (You probably don't; you want VP9). Or vice versa? You can't fully disable one easily, but you can reduce features:
