Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ALSA tools for build-root
Date: Sat, 2 Jun 2007 12:32:47 +0200	[thread overview]
Message-ID: <20070602103246.GL12010@aon.at> (raw)
In-Reply-To: <46613FBE.7080709@teamboyce.co.uk>

On Sat, Jun 02, 2007 at 11:00:30AM +0100, Rod Boyce wrote:
>All,
>
>I have also added alsa-tools to build-root and attached is the patch.  
>These tools have a lot of dependencies that I am not using the tools 
>that build fine for me I have defaulted to 'default y' in the Config.in 
>file, all tools that depend on X, GTK, or some other library I am not 
>using I have set 'default n' there are also tools that are going to 
>require a custom target that my makefile does not do anything with these 
>are all commented out in the config file.  The makefile is quite simple 
>I have a macro that creates a target for each simple selected tool the 
>tools are selected from the configure script this was the simplest way I 
>could think of doing the simple targets for this tool set.  I have not 
>looked at what is needed for the more complicated targets and I don't 
>plan on using then.  But I have left them in for the next to make the 
>job easier for the next person hopefully.
>
>Regards,
>Rod Boyce

>Index: package/alsa-tools/alsa-tools.mk
>===================================================================
>--- package/alsa-tools/alsa-tools.mk	(revision 0)
>+++ package/alsa-tools/alsa-tools.mk	(revision 0)
>@@ -0,0 +1,134 @@
>+#############################################################
>+#
>+# ALSA Tools
>+#
>+#############################################################
>+ALSA-TOOLS_VERSION := 1.0.14rc3
>+ALSA-TOOLS_SOURCE := alsa-tools-$(ALSA-TOOLS_VERSION).tar.bz2
>+ALSA-TOOLS_SITE := ftp://ftp.alsa-project.org/pub/tools/
>+ALSA-TOOLS_DIR := $(BUILD_DIR)/$(patsubst %.tar.bz2,%,$(ALSA-TOOLS_SOURCE))

Also, i'm curious where you picked up this notion of setting the
FOO_DIR.

The established way is a simple
FOO_DIR:=$(BUILD_DIR)/foo-$(FOO_VERSION)

  parent reply	other threads:[~2007-06-02 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 10:00 [Buildroot] ALSA tools for build-root Rod Boyce
2007-06-02 10:26 ` Bernhard Fischer
2007-06-02 10:40   ` Rod Boyce
2007-06-02 10:32 ` Bernhard Fischer [this message]
2007-06-02 11:06   ` Rod Boyce
2007-06-06  6:38 ` Hans-Christian Egtvedt

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=20070602103246.GL12010@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