From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Jaroslav Kysela <perex@suse.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: OSS API redirector
Date: Thu, 18 Mar 2004 14:12:46 +0000 [thread overview]
Message-ID: <4059AE5E.7030703@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0403181015270.1835@pnote.perex-int.cz>
Jaroslav Kysela wrote:
> Hi all,
>
> I would like to point all developers to the OSS API redirector
> which is in our alsa-oss package. It's universal piece of code which can
> redirect all OSS API calls (actually mixer & PCM API only) to any shared
> library.
>
> Pros:
> - no more LD_PRELOAD hacks
> - any library can be used directly as endpoint
> - when used more applications will work (also some which does not work
> with LD_PRELOAD hack)
>
> Drawbacks:
> - still no fopen/fclose/fwrite/fread solution
> - applications must be a little bit modified
>
> -----
> Jaroslav Kysela <perex@suse.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, SuSE Labs
>
What is the conclusion regarding fopen/fclose/fwrite/fread.
Can it be done?
Cheers
James
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-18 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 9:32 OSS API redirector Jaroslav Kysela
2004-03-18 14:12 ` James Courtier-Dutton [this message]
2004-03-18 21:37 ` David Lloyd
2004-03-21 22:53 ` James Courtier-Dutton
2004-03-22 9:27 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4059AE5E.7030703@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox