From alsa-devel-owner@alsa.jcu.cz  Thu Nov 19 20:05:32 1998
Received: from downstairs.db-bbs.com (root@58.usr02.shef.dialup.force9.net [195.166.132.186])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id UAA20657
	for <alsa-devel@alsa.jcu.cz>; Thu, 19 Nov 1998 20:03:12 +0100
Received: by sandy.force9.co.uk
	via sendmail from stdin
	id <m0zgGUY-000BK3C@downstairs.db-bbs.com> (Debian Smail3.2.0.101)
	for alsa-devel@alsa.jcu.cz; Wed, 18 Nov 1998 22:54:30 +0000 (GMT) 
Message-Id: <m0zgGUY-000BK3C@downstairs.db-bbs.com>
From: chrisb@sandy.force9.co.uk (Chris Butler)
Subject: alsa-lib and automake
To: alsa-devel@alsa.jcu.cz
Date: Wed, 18 Nov 1998 22:54:30 +0000 (GMT)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Hi,

I've just checked in to the alsa-lib CVS tree a fairly big change. The
alsa-lib package now uses automake and libtool to build. Hopefully,
you won't notice much difference, except for the fact that you can do
a VPATH build (build in another dir), etc..

The procedure for compiling from CVS is the same. Check-out, run
autoconf, then configure/make. The only difference (as I said above)
is that you can build in another directory (call configure from there)
- this is helpful when dealing with CVS. You can also use the options
--disable-shared and --disable-static (both are currently on by
default, but this can be changed) to disable building shared or static
libraries respectively.

I've tested it as far as I can (checked it out to a fresh directory
and built it), so I think it will work. Just make sure that you re-run
autoconf after doing a cvs update.

I plan to do the same for the alsa-utils, and possible even the
alsa-driver (although this will be more difficult), but I'm not sure
when this will be, because I've been a bit busy lately.

--
Chris Butler
<chrisb@sandy.force9.co.uk>

