Hello,

>From what I understood, the API did not change at all (they managed to keep
header compatibility as well so a stream encoded with 1.0.x can be decoded
by 1.2beta1 and vice versa)

I did not need to modify the phapi code in order to link with the new
compiled speex lib so it should be backward compatible even for
distributions that ship the 1.0.x and you should not expect problems.

That being said, we'll need to keep this upgrade in mind after the commit if
ever one of the packaging script goes wild. I'll try to update the speex
part of the wiki at the same time to keep a log of this

Jerome

-----Message d'origine-----
De : Gianluca Sforna [mailto:[EMAIL PROTECTED] 
Envoyé : jeudi 21 septembre 2006 09:14
À : Jérôme WAGNER
Cc : [email protected]
Objet : Re: [Wengophone-devel] upgrade speex 1.2beta1

On 9/20/06, Jérôme WAGNER <[EMAIL PROTECTED]> wrote:
> In order to avoid doing it without notice and check with you the impact of
> this choice, here is the news:
>
> I am going to upgrade the wifo/phapi/speex source code to the 1.2beta1
> version of speex. This is the recommended version for speex now.

Thank a lot. Really appreciated...

>
> Ps1: please don't react on the fact that this lib should not be here at
all.
> I agree with that. This will need to be done in a future refactoring of
all
> external libs.
:D

Should we expect breakage if trying to compile/link with a system
library? IOW, was the API changed from 1.0 to 1.2?

I am asking because I think distributions will have 1.0.x (right now,
my Fedora Core 5 has 1.0.5) at least until that 1.2 becomes final.

_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to