From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Compiling but not installing Alsa Date: Mon, 09 Dec 2002 12:15:06 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <1039368265.1410.42.camel@Godzilla> <1039368955.1410.46.camel@Godzilla> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <1039368955.1410.46.camel@Godzilla> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Mark Knecht Cc: Alsa-Devel List-Id: alsa-devel@alsa-project.org 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