Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rod Boyce <buildroot@teamboyce.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] ALSA for build root
Date: Sat, 26 May 2007 15:45:18 +0100	[thread overview]
Message-ID: <465847FE.6050304@teamboyce.co.uk> (raw)
In-Reply-To: <4656F77D.30303@teamboyce.co.uk>

Rod Boyce wrote:
> All,
>
> I have been adding ALSA to the build root package system I am only able 
> to test on a x86 platform.  Is anybody else interested in ALSA for 
> build-root?  I have also been adding libogg and libvorbis would it be OK 
> if I submitted a combined patch or would you prefer 2 separate patches?  
> Is anybody else working on this who would like an advanced copy to test 
> out and or compare against?
>
> This would include the following packages:
> alsa-lib-1.0.14rc4
> alsa-utils-1.0.14rc4
> libogg-1.1.3
> libvorbis-1.1.2
>
>
> Regards,
> Rod Boyce
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
>   
All,

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.

Regards,
Rod Boyce
-------------- next part --------------
A non-text attachment was scrubbed...
Name: alsa.patch
Type: text/x-patch
Size: 23409 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070526/0dee6bb5/attachment.bin 

  parent reply	other threads:[~2007-05-26 14:45 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 ` Rod Boyce [this message]
2007-05-29  7:03   ` [Buildroot] ALSA for build root 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     ` [Buildroot] ALSA for build root Bernhard Fischer
2007-05-29 23:01       ` 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=465847FE.6050304@teamboyce.co.uk \
    --to=buildroot@teamboyce.co.uk \
    --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