Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Ciaccia <ciacciax@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Static build of alsa-lib
Date: Fri, 16 Mar 2007 16:20:43 +0100	[thread overview]
Message-ID: <s5htzwlusdw.wl%tiwai@suse.de> (raw)
In-Reply-To: <393830.60990.qm@web31012.mail.mud.yahoo.com>

At Fri, 16 Mar 2007 08:11:20 -0700 (PDT),
Ciaccia wrote:
> 
> Hi Takashi,
> Thanks for the answer. To I need both the patches or
> just the first one?

The second one is for the fix to build without any extra pcm plugins
(i.e. --with-pcm-plugins=hw or so).

> Which alsa-lib release should I
> use with the patch, 1.0.13?

Better to use the latest HG version.

> PS: sorry, what is the HG tree?

HG (Mercurial) is what we are currently using as the source tree
management.  See www.alsa-project.org download section.

The daily snapshot tarballs are available at
	ftp://ftp.suse.com/pub/projects/alsa/snapshot/


Takashi

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-03-16 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 13:17 Static build of alsa-lib Ciaccia
2007-03-16 14:18 ` Takashi Iwai
2007-03-16 14:24   ` Takashi Iwai
2007-03-16 15:11     ` Ciaccia
2007-03-16 15:20       ` Takashi Iwai [this message]
2007-03-17 10:13   ` Ciaccia
2007-03-20 10:48     ` Takashi Iwai
2007-03-20 12:00       ` Rene Herman
2007-03-20 15:13       ` Ciaccia
2007-03-20 16:01         ` [Alsa-devel] " Takashi Iwai
2007-03-21 19:00           ` Ciaccia

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=s5htzwlusdw.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ciacciax@yahoo.com \
    /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