From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: "focus.luo" <focus.luo@linux.intel.com>
Cc: Focus Luo <focus.luo@intel.com>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] alsabat: automation test scripts
Date: Tue, 09 Aug 2016 10:40:43 +0100 [thread overview]
Message-ID: <1470735643.31650.21.camel@loki> (raw)
In-Reply-To: <s5h37me484t.wl-tiwai@suse.de>
On Tue, 2016-08-09 at 11:13 +0200, Takashi Iwai wrote:
> On Tue, 09 Aug 2016 11:24:59 +0200,
> focus.luo wrote:
> >
> >
> > On 2016年08月09日 16:01, Takashi Iwai wrote:
> > > On Tue, 09 Aug 2016 09:47:48 +0200,
> > > Liam Girdwood wrote:
> > >> On Tue, 2016-08-09 at 09:10 +0200, Takashi Iwai wrote:
> > >>> On Mon, 08 Aug 2016 05:00:24 +0200,
> > >>> focus.luo@linux.intel.com wrote:
> > >>>> From: Focus Luo <focus.luo@intel.com>
> > >>>>
> > >>>> This patch includes automated test scripts for linux audio driver
> > >>>> based on alsa-lib interface by using alsabat as test tool.
> > >>>> It supports analog and display(HDMI/DP) audio test.
> > >>>> The package needs the alsa-utils, alsa-lib installed environment.
> > >>>>
> > >>>> Signed-off-by: Focus Luo <focus.luo@intel.com>
> > >>> You need to modify Makefile.am, too. Otherwise these contents won't
> > >>> be included in the release.
> > >>>
> > >> Where would be a good place to install the scripts ? I think the
> > >> intention from Focus is that these are local scripts for use by devs and
> > >> not really for everyone. They could perhaps go in
> > >> ${prefix}/share/alsa/abat/tests ?
> > > Well, if this is merely an example, we don't have to install it, but
> > > just keep it in tarball, too.
> > In future, we will continue to add/update some scripts in the the
> > folder of "/alsa-utils/bat/tests" for alsabat. So would it be better
> > to keep it as folder but not tarball?
>
> No, I meant that your contents won't be included in alsa-utils release
> unless you add properly to Makefile.am. automake won't pack the
> unlisted files via "make dist".
>
Focus, you will need to add the scripts using automake (to Makefile.am)
e.g.
noinst_SCRIPTS = \
script1 \
script2
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-08-09 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 3:00 [PATCH 0/2] alsabat: test scripts and reference amixer config files focus.luo
2016-08-08 3:00 ` [PATCH 1/2] alsabat: automation test scripts focus.luo
2016-08-09 7:10 ` Takashi Iwai
2016-08-09 7:47 ` Liam Girdwood
2016-08-09 8:01 ` Takashi Iwai
2016-08-09 9:24 ` focus.luo
2016-08-09 9:13 ` Takashi Iwai
2016-08-09 9:40 ` Liam Girdwood [this message]
2016-08-08 3:00 ` [PATCH 2/2] alsabat: add amixer config files focus.luo
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=1470735643.31650.21.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=focus.luo@intel.com \
--cc=focus.luo@linux.intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).