On 9/26/07, logan <[EMAIL PROTECTED]> wrote:
>
>  Hi,
>
> Last time I did it then I also needed to add libspeex.lib to the
> additional libraries of the plgspeex project as it wasn't listed there.
>

Aha, yes, in the release build I see that 'libspeex.lib' was not added to
AdditionalDependencies.  I have now fixed that.

Between, I was also getting an assertion in sipxConfigGetNumAudioCodecs
> during the debug build, looks to me that it couldn't find the codecs, but I
> had all the codec plugins and libspeex.dll placed in the output folder.
>

Ahh, I missed some additional instructions:
Put libspeex.dll in the same directory as the generated plugin dlls --
sipXmediaLib/bin, and I believe that should solve the codec load problem.

I added a post build step to the codec plugin build to copy over the speex
dll to the sipXmediaLib/bin directory, but again, I failed to add it to the
release build, so I'm not surprised you are running into these problems.
This is now fixed.

When building speex, please build with the 'Release_Dynamic' target, as the
post build step assumes that, and, actually, I believe that is the only
target that generates a DLL anyway.

I've made a bunch of changes to the plgspeex-msvc8.vcproj project file in
response to this discussion that should fix the issues -- r10221 and r10222
are the revisions to look at:

http://scm.sipfoundry.org/viewsvn/sipX?view=rev&revision=10221
http://scm.sipfoundry.org/viewsvn/sipX?view=rev&revision=10222

----- Original Message -----
> *From:* Keith Kyzivat <[EMAIL PROTECTED]>
> *To:* Xiaoming wang <[EMAIL PROTECTED]>
> *Cc:* [email protected]
> *Sent:* Wednesday, September 26, 2007 1:19 AM
> *Subject:* Re: [sipxtapi-dev] sipXtapi' speex for VC 2005
>
> Sounds like you don't have the speex sources expanded in
> sipXmediaLib/contrib/libspeex
>
>
>    - Grab a copy of the latest speex code from
>    http://www.speex.org/downloads/
>    - Expand it into the sipXmediaLib/contrib/libspeex directory
>    - Load the libspeex *VS2003* project from speex (there's a VS2005
>    project, but I've been told the VS2003 project is more up to date, and 
> works
>    fine)
>    - Build speex dll
>
> You should now be able to build the speex plugin.
>
> On 9/25/07, Xiaoming wang < [EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Hi Alls,
> >
> > Today I checkout then branches\last sipXTaip.
> >
> > I complie it in VC 2005, I got Error :
> > ------ Build started: Project: plgspeex-msvc8, Configuration: Release
> > Win32 ------
> >
> > Compiling...
> >
> > PlgSpeex.c
> >
> > Linking...
> >
> > Creating library Release/plgspeex.lib and object Release/plgspeex.exp
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_preprocess_ctl referenced in function _universe_speex_init
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_preprocess_state_init referenced in function _universe_speex_init
> >
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_encoder_ctl referenced in function _universe_speex_init
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_encoder_init referenced in function _universe_speex_init
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_bits_init
> > referenced in function _universe_speex_init
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_decoder_ctl referenced in function _universe_speex_init
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_decoder_init referenced in function _universe_speex_init
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_lib_get_mode referenced in function _universe_speex_init
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_bits_destroy referenced in function _universe_speex_free
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_encoder_destroy referenced in function _universe_speex_free
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_decoder_destroy referenced in function _universe_speex_free
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_decode_int
> > referenced in function _universe_speex_decode
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_bits_read_from referenced in function _universe_speex_decode
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_bits_write
> > referenced in function _universe_speex_encode
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_encode_int
> > referenced in function _universe_speex_encode
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_preprocess
> > referenced in function _universe_speex_encode
> >
> > PlgSpeex.obj : error LNK2019: unresolved external symbol
> > _speex_bits_reset
> > referenced in function _universe_speex_encode
> >
> > ..\..\..\..\bin\codec_speex.dll : fatal error LNK1120: 17 unresolved
> > externals
> >
> > 1>Build log was saved at
> >
> >
> > "file://c:\martin\sflphone\branches\sipxtapi\sipXmediaLib\src\mp\codecs\plgs
> > peex\Release\BuildLog.htm"
> >
> > plgspeex-msvc8 - 18 error(s), 0 warning(s)
> >
> > ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
> > ==========
> >
> >
> >
> > I like to know which speex version is compatible with the latest
> > sipXTapi ?
> >
> >
> > Thanks.
> >
> >
> >
> > Martin
> >
> > _______________________________________________
> > sipxtapi-dev mailing list
> > [email protected]
> > List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
> >
>
>
>
> --
> Keith Kyzivat
>
> SIPez LLC.
> SIP VoIP, IM and Presence Consulting
> http://www.SIPez.com
> tel: +1 (617) 273-4000
>
> ------------------------------
>
> _______________________________________________
> sipxtapi-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
>
>


-- 
Keith Kyzivat

SIPez LLC.
SIP VoIP, IM and Presence Consulting
http://www.SIPez.com
tel: +1 (617) 273-4000
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/

Reply via email to