It is... --disable-libvpx There shouldn't be much reason for it, if you have a good reason due to a build issue I'd like to try to resolve that. I have seen issues that people need to install yasm or nasm for libyuv, and some people have had to upgrade toolchain on older distros. What issue/concern are you having?
On Mar 16, 2016, at 3:14 PM, Ben Hood <0x6e6562@gmail.com> wrote:
Is libvpx optional, i.e. is there a way to disable libvpx support in the build (e.g. by supplying --without-libvpx to the configure script)?
On Wed, Feb 24, 2016 at 11:49 PM, Michael Jerris <mike@jerris.com> wrote:
please note this important change that went into master today. As of today, we are no longer using system versions of libyuv and libvpx due to major conflicts with system versions of these libraries. These are now built static into the freeswitch core. Also note, mod_vpx no longer exists, it is automatically loaded as part of the core and you will no longer have mod_vpx.so or have to manually load it. I'll have more details coming, but let me know if you have any questions. Please note for anyone doing cross compiling, this probably needs a bit more work for you, I'll be working on fixing that this week.
Mike