What is the error you are getting when you try to build current master. There is no need for a flag to disable libspeex, you just don't build the module.
On Mar 16, 2016, at 5:36 PM, Ben Hood <0x6e6562@gmail.com> wrote:
Thanks for the heads up about the name of the disabling flag - that seems to have worked in the sense that the build now goes past an issue I was seeing with libvpx.
The problem I am having is trying to get c422cddb to compile on Solaris 11.3, which I appreciate is not a supported platform. I've been using 2d46e0af which I successfully compiled and have been running for a few weeks, but that version doesn't appear to have the libvpx refactoring in it. In addition, this time round I was attempting to supply custom versions of the dependencies such as libsndfile, rather than depend on CSW packaging.
Anyway, I think the issue with the build is more of a libvpx thing than a FS issue, which is why I raised a question on their list:
https://groups.google.com/a/webmproject.org/d/msg/webm-discuss/jrKh-cN5tS4/9...
So I guess the fundamental issue is I'm trying to do something that isn't supported - so I appreciate that there's probably not too much time that you can dwell on this.
BTW can I disable speex support by passing --disable-libspeex or similar? Is there a list of the names of features that can be turned off during compilation in one of the build files?
On Wed, Mar 16, 2016 at 8:55 PM, Michael Jerris <mike@jerris.com> wrote:
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org