All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Maarten de Boer <mdeboer@iua.upf.es>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: pcm_jack and jack chicken-and-egg situation
Date: Wed, 05 Mar 2003 10:49:02 +0100	[thread overview]
Message-ID: <s5hel5mf8j5.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030305101157.3373dbfc.mdeboer@iua.upf.es>

At Wed, 5 Mar 2003 10:11:57 +0100,
Maarten de Boer wrote:
> 
> Bob Ham <rah@bash.sh> wrote:
> > The new pcm_jack thing presents a bit of a chicken and egg problem; I
> > just compiled alsa-lib twice because jack depends on alsa-lib and if you
> > configure alsa-lib with jack support, it depends on jack.  Would it be
> > possible for pcm_jack to be distributed seperately?
> 
> Hi Bob,
> 
> That's indeed a problem I did not realize... And there is an another,
> related problem, which is that with binary distributions, you have 
> to either distribute to versions, one linked against jack and one not
> linked against jack.
> 
> The ALSA plugin's are all compiled into the library. It would indeed be
> nice if each plugin would be a seperate shared object.

you can specify the so file and the function name via pcm_type
definition:

	pcm_type.foo {
		comment foo type plugin
		lib /usr/lib/libfoo.so
		open my_foo_open
	}


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2003-03-05  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05  0:02 pcm_jack and jack chicken-and-egg situation Bob Ham
2003-03-05  9:03 ` Takashi Iwai
2003-03-05  9:11 ` Maarten de Boer
2003-03-05  9:49   ` Takashi Iwai [this message]

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=s5hel5mf8j5.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mdeboer@iua.upf.es \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.