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@xxxxxxxxxxxxxxx wrote:
> >>>> From: Focus Luo <focus.luo@xxxxxxxxx>
> >>>>
> >>>> 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@xxxxxxxxx>
> >>> 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".
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
