From: Rod Boyce <buildroot@teamboyce.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] ALSA for build root Part 2
Date: Wed, 30 May 2007 23:29:03 +0100 [thread overview]
Message-ID: <465DFAAF.3030704@teamboyce.co.uk> (raw)
In-Reply-To: <20070529200050.GA30684@aon.at>
Bernhard Fischer wrote:
> 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:
>>>
>
> Rod, care t osend an updated patch taking Hans-Christian's comments
> (thanks for those!) into account?
>
> TIA,
>
>
All,
Attached is an updated patch that does not offend the sensibilities of
other ALSA people working on build root. This is just alsa-lib and
alsa-utils I will send out a patch for more alsa stuff latter. This
outputs to $(STAGING_DIR)/usr/lib which on my build happens to be a link
back to $(STAGING_DIR)/lib. I have also removed the device links that I
was putting in the dev directory I had not removed this since I switched
over to udev. Just --prefix=/usr did not fix all paths all of the time
although I think that I have the minimum custom options for configure
and install targets for both utilities and library makefile fragments
now. I also figured out what the "basename nonsense" was and while I
approve of the intent I used a more makefile way of doing the same thing.
Hopefully this is a more acceptable patch, if anybody has some more
suggestions then perhaps they would like to contribute their own ALSA
patch's so we can either pick the best or merge and get the best of both
worlds and produce a better build-root system.
Regards,
Rod Boyce
-------------- next part --------------
A non-text attachment was scrubbed...
Name: alsa.patch
Type: text/x-patch
Size: 8564 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070530/bcc6f0ad/attachment.bin
next prev parent reply other threads:[~2007-05-30 22:29 UTC|newest]
Thread overview: 28+ 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 ` Rod Boyce [this message]
2007-06-06 7:47 ` [Buildroot] ALSA for build root Part 2 Hans-Christian Egtvedt
2007-05-29 20:04 ` [Buildroot] ALSA for build root Bernhard Fischer
2007-05-29 23:01 ` 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=465DFAAF.3030704@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