From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ALSA for build root
Date: Tue, 29 May 2007 22:04:08 +0200 [thread overview]
Message-ID: <20070529200408.GB30684@aon.at> (raw)
In-Reply-To: <1180422192.32245.22.camel@localhost.localdomain>
On Tue, May 29, 2007 at 09:03:12AM +0200, Hans-Christian Egtvedt wrote:
>On Sat, 2007-05-26 at 15:45 +0100, Rod Boyce wrote:
>> Rod Boyce wrote:
>
><cut intro about alsa patches>
>
>> As promised attached is a patch to add ALSA packages to build root I
>> have only tested on i386 but it seems to work for me. This patch is
>> against the latest SVN repository No. 18694. I have not tested the
>> alsa-tools well and in-fact because I am not using X or GTK most will
>> not compile I have disabled all the the ac3dec by default. Also I am
>> assuming the latest version of ALSA and a compatible kernel.
>
>I am working on the exactly same package (alsa + alsa-util) for
>buildroot, so far testing on an AVR32 platform.
>
>> diff -Nu --recursive --exclude=.svn --exclude=config --exclude=libogg
>> --exclude=libvorbis ../trunk/package/alsa-lib/alsa-lib.mk
>> package/alsa-lib/alsa-lib.mk
>> --- ../trunk/package/alsa-lib/alsa-lib.mk 1970-01-01
>> 01:00:00.000000000 +0100
>> +++ package/alsa-lib/alsa-lib.mk 2007-05-26 08:17:42.849975524
>> +0100
>> @@ -0,0 +1,135 @@
>> +#############################################################
>> +#
>> +# ALSA library
>> +#
>> +#############################################################
>> +
>> +ALSA-LIB_VERSION=1.0.14rc4
>> +ALSA-LIB_SOURCE=alsa-lib-$(ALSA-LIB_VERSION).tar.bz2
>> +ALSA-LIB_SITE=ftp://ftp.alsa-project.org/pub/lib/
>> +ALSA-LIB_DIR=$(BUILD_DIR)/${shell basename
>> $(ALSA-LIB_SOURCE) .tar.bz2}
And please don't forget to strip this basename nonsense off.
thanks,
next prev parent reply other threads:[~2007-05-29 20:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 14:49 [Buildroot] ALSA for build root Rod Boyce
2007-05-25 15:13 ` Daniel Laird
2007-05-25 18:56 ` Peter at busybox.net
2007-05-25 19:03 ` Stuart Wood
2007-05-25 19:23 ` [Buildroot] Package selection question Tom
2007-05-25 19:51 ` Yann E. MORIN
2007-05-25 20:38 ` Bernhard Fischer
2007-05-25 20:45 ` Yann E. MORIN
2007-05-25 21:10 ` Tom
2007-05-26 9:23 ` Bernhard Fischer
2007-05-26 10:22 ` Yann E. MORIN
2007-05-25 20:03 ` Bernhard Fischer
2007-05-25 20:59 ` Tom
2007-05-26 9:50 ` Bernhard Fischer
[not found] ` <4657D353.7030704@gmail.com>
2007-05-26 6:33 ` [Buildroot] mpfr error on cygwin for arm Tom
[not found] ` <4657D933.8060109@gmail.com>
2007-05-26 9:48 ` Bernhard Fischer
2007-05-30 3:07 ` Tom
2007-05-30 9:47 ` Bernhard Fischer
2007-05-30 16:03 ` Tom
2007-05-31 7:33 ` Tom
2007-05-25 20:05 ` [Buildroot] Package selection question Bernhard Fischer
2007-05-26 14:45 ` [Buildroot] ALSA for build root Rod Boyce
2007-05-29 7:03 ` Hans-Christian Egtvedt
2007-05-29 20:00 ` Bernhard Fischer
2007-05-30 22:29 ` [Buildroot] ALSA for build root Part 2 Rod Boyce
2007-06-06 7:47 ` Hans-Christian Egtvedt
2007-05-29 20:04 ` Bernhard Fischer [this message]
2007-05-29 23:01 ` [Buildroot] ALSA for build root Rod Boyce
[not found] <KRKghF7Kp6q2.1lf2WpS3@mailout.dof.se>
2007-05-26 14:35 ` Rod Boyce
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=20070529200408.GB30684@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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