search for: speex_get_lib_version

Displaying 3 results from an estimated 3 matches for "speex_get_lib_version".

2004 Aug 06
4
Re: does installed lib support _int()s ?
Hi, Right now, I'm thinking of adding a speex_lib_ctl() call that would support SPEEX_GET_VERSION (and return a string) or SPEEX_GET_MAJOR_VERSION and SPEEX_GET_MINOR_VERSION (and return ints). I'm open to other suggestions though. If there's anything you'd like to see in the API for 1.2, say it now. ...and no, I won't add a speex_do_all_the_work_for_me() call :)
2004 Aug 06
0
Re: does installed lib support _int()s ?
...turn ints). > I'm open to other suggestions though. If there's anything you'd like to > see in the API for 1.2, say it now. ...and no, I won't add a > speex_do_all_the_work_for_me() call :) Sounds reasonable. You could also overload the existing speex_*_ctl() calls to take SPEEX_GET_LIB_VERSION, SPEEX_GET_LIB_MAJOR_VERSION, etc. What people are really asking for here is a way to determine at for conditional compilation (i.e. at configure time) what calls are available. One traditional way to do that is just to provide #defines for SPEEX_MAJOR_VERSION and so on in the header. If you'r...
2004 Aug 06
2
Re: does installed lib support _int()s ?
> Sounds reasonable. You could also overload the existing speex_*_ctl() > calls to take SPEEX_GET_LIB_VERSION, SPEEX_GET_LIB_MAJOR_VERSION, etc. > > What people are really asking for here is a way to determine at for > conditional compilation (i.e. at configure time) what calls are > available. Runtime methods would be nice too, for prebuilts to be able to determine what they can call and w...