Re: esd problem
- From: Michael Lausch <mla gams co at>
- To: "Brandon S. Allbery" <allbery hilfy ece cmu edu>
- Cc: gnome-list gnome org
- Subject: Re: esd problem
- Date: Thu, 03 Dec 1998 18:36:46 +0100
>>>>> "ba" == Brandon S Allbery <allbery@hilfy.ece.cmu.edu>
>>>>> wrote the following on Thu, 03 Dec 1998 12:25:10 -0500
ba> In message <199812031607.RAA16642@loki.gams.co.at>, Michael Lausch writes:
ba> +-----
ba> | I lokked around a little bit in the gnome-core sources and found that
ba> | rebuilding gnome-core changes the gnome-config program so that the
ba> | correct libraries are used.
ba> |
ba> | Wouldn't it be much simpler to call esd-config in the gnome-config
ba> | shell script?
ba> +--->8
ba> Simpler, but *wrong* if the visible esd development kit doesn't match the one
ba> gnome-core was built with.
I don't think so. the esound API and ABI should stay the same between
different implementations of esound.
I think to have the esound client library linked against sound system
specific libraries is a big problem. you can't rely on the fact that
only one sound system is supported under a specific OS. It's easy to
start the right esound daemon and it's a little harder (and i think it
might become a maintenance nightmare) to have all gnome programs
linking against the correct dynamic sound lib.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]