From: Peter Kirk <pwk.linuxfan@gmx.de>
To: alsa-devel@lists.sourceforge.net
Cc: Jaroslav Kysela <perex@suse.cz>
Subject: Re: making aoss able to wrap fopen() calls
Date: Fri, 6 Feb 2004 12:28:05 +0100 [thread overview]
Message-ID: <200402061228.12714.pwk.linuxfan@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0402051748390.1864@pnote.perex-int.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Donnerstag, 5. Februar 2004 17:49 schrieb Jaroslav Kysela:
> > Could you point me to a good idea of implementing this ? On irc I was
> > discussing doing a libc wrapper that replaces the fopen calls with some
> > substitute (that aoss can handle), but I'm not sure if its the way to go.
> >
> > Please tell me how it can be achieved.
>
> The whole libaoss is based on glibc wrappers (open, close, ioctl, write,
> read, mmap) so follow this rule ;-)
Right,
I have done some looking at source code, and have found the places I needed to
find (in alsa-oss.c).
Two questions:
(1) Is my assumtion right, that I will have to write substitute functions for
fopen(), fclose(), fread() and fwrite() ?
(2) My current approach is to "translate" the f* calls into calls that can be
handled already. Is this a good idea ?
Peter
- --
A critic is a bundle of biases held loosely together by a sense of taste.
-- Whitney Balliett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAI3pJg2ieGvTmHiURAhCoAKCbo0VxbUDm85MBiR9ZpqX3HhDUxgCdFya4
+2bewyW36EcCJksr9jpWsOY=
=1X1j
-----END PGP SIGNATURE-----
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-02-06 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 16:26 making aoss able to wrap fopen() calls Peter Kirk
2004-02-05 16:49 ` Jaroslav Kysela
2004-02-06 11:28 ` Peter Kirk [this message]
2004-02-09 14:07 ` Jaroslav Kysela
2004-02-09 18:19 ` Peter Kirk
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=200402061228.12714.pwk.linuxfan@gmx.de \
--to=pwk.linuxfan@gmx.de \
--cc=alsa-devel@lists.sourceforge.net \
--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