[Angstrom-devel] [FWD oe-commit] flite oss vs alsa

[Paul Sokolovsky]

Hello Junqian,

Sunday, January 6, 2008, 3:16:25 PM, you wrote:

> On 01/06/2008 05:38 AM, Koen Kooi wrote:
>> Junqian Gordon Xu schreef:
>> | Please comment on this change, which one Angstrom want to default to,
>> | how to handle conflicts, etc?
>> 
>> I'm hard pressed to find any >2.6.16 platform that doesn't support alsa.
>> The only people that are making a fuzz about alsa sucking are all 4Front
>> employees, so I'd say "go for alsa".

> I should have provided more info regarding the flite alsa patch by Lukas
> Loehrer. The following is my understaing (could be wrong):

> 1) with (--with-audio=alsa) or without (--with-audio=oss) the alsa 
> patch, flite is built against library provided by alsa-oss package.
> 2) The alsa patch adds alsa API to flite natively, but blocks the shared
> flite libraries to use other API by removing the __init_** hookup 
> functions. (my description may not be technically correct, but you got
> the idea). Hence, speech-dispatch fails when trying to implement it's 
> own alsa API with the shared flite libraries.

> The best solution is to ask Lukas Loehrer (I'll contact him, or any 
> volunteers :) to update his alsa patch and make it more flexible. 
> However, I'm not having my hopes high based on the style of his hacks.

  That's the impression I got too - that's just a random hack. Using
ALSA directly is nice thing, but at what price? Someone who really
cares about that should probably clean up patches first before
applying them to OE at all, IMHO.

>> Do we want this in the stable branch as well?

> stable branch should be fine as alsa is the default.
> dev branch (Angstrom-prefered) can use flite-alsa as default (people who
> what to use application, such as speech-dispatch, can override it with
> flite).

> Regards
> Gordon

[]

-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com