All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Knecht <markknecht@attbi.com>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Compiling but not installing Alsa
Date: Mon, 09 Dec 2002 12:15:06 +0100	[thread overview]
Message-ID: <s5hsmx78mv9.wl@alsa2.suse.de> (raw)
In-Reply-To: <1039368955.1410.46.camel@Godzilla>

At 08 Dec 2002 09:35:55 -0800,
Mark Knecht wrote:
> 
> Hi,
>    I did my first Alsa CVS download this morning just to take a look at
> the code. I am a PlanetCCRMA user, but wanted to know more about Alsa.
> 
>    I have not yet found a README or INSTALL file on how to do a build.
> Are there any written instructions in the CVS tree?

it's found on alsa-driver directory.
in short, run cvscompile script on the top of alsa-driver tree.

	% ./cvscompile --with-cards=xxx

and it will generate the configure script, run it and make driver
modules.

you have to get both alsa-driver and alsa-kernel cvs trees
beforehand, since alsa-kernel is separate from alsa-driver, while the
alsa-driver tarball includes both.

> 
>    I looked at the Makefile, which I can't read well, and I get the
> feeling that the default operation would be to build AND install the
> code. As a RPM based user I would like to build the code, but not
> install it until the Planet updates the appropriate RPM.

the rpm depends on the distributor.
a general spec file can be found on alsa-driver/utils directory,
though.


ciao,

Takashi


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

      reply	other threads:[~2002-12-09 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1039368265.1410.42.camel@Godzilla>
2002-12-08 17:35 ` Compiling but not installing Alsa Mark Knecht
2002-12-09 11:15   ` 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=s5hsmx78mv9.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=markknecht@attbi.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 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.