--disable-vp8-encoder --disable-vp9-decoder When cross-compiling, specify exactly the architecture:
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. bloat libvpx
From the perspective of a desktop Linux user: libvpx is lean, fast, and necessary. The "bloat" is actually future-proofing . In this context, it’s a technical observation
From the perspective of an IoT developer with 32 MB of total flash storage: The default libvpx is a nightmare of redundant symbol tables and CPU dispatchers that will never fire on their hardware. The "bloat" is actually future-proofing
./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.
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.