The client API is in the client/ subdirectory and you
can link with it as `-lgdam-common -lgdam-client'.
The headers aren't in any package (so compiling other clients
will have to depend on the users having the gdam source code
around, unfortunately), but breaking the distribution into a bunch of
pieces is slated for right after the next release.
(basically the pieces will be: client-libraries,
server-runtime, server-dev, client-dev, "launcher" - the gui)
Mostly you'll have to learn the api through the `gdam-dev.sgml' file,
and through the header files. We are working on reference
documentation using a program named codoc, but it's quite skeletal
at the moment.
GDAM is intended to be a general purpose audioserver (ie. to merely
mix and revolumize mp3s no float/fixed conversion is done)
while scaling (with plugins) to as much complexity as we can implement :)
It depends upon GTK+ as a backbone for the plugins.
I forgot to mention last time that of course GDAM would
greatly appreciate any assistance anyone would care to give
us, which was supposed to be the main point ;)
- Dave
On Wed, 27 Sep 2000, Kai Vehmanen wrote:
> On Tue, 26 Sep 2000, David Benson wrote:
>
> >> Looking at the other canditates, esd is still dead, X-audioserver list
> > fwiw, GDAM is principally in this category.
> > (We just happen to ship a very large and complex client --
> > we also distribute two command-line-only clients...)
>
> Ok, this is new to me. Have you published any client APIs (or do you
> intend to)?
>
> --
> . http://www.eca.cx ... [ audio software for linux ] /\ .
> . http://www.eca.cx/aivastus ... [ aivastus net radio ] /\ .
> . http://www.eca.cx/sculpscape [ my armchair-tunes mp3/ra/wav ]
>
>
