Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: simon.marchi@polymtl.ca (Simon Marchi)
Subject: [lttng-dev] [PATCH 1/3] tests/lib/Makefile.am: Remove test_seek_empty_packet and test_seek_big_trace from SCRIPT_LIST
Date: Thu, 28 Apr 2016 12:44:14 -0400	[thread overview]
Message-ID: <1d03bf34bd523c31ab8d32e7abda56ec@simark.ca> (raw)
In-Reply-To: <1804225761.72412.1461860179512.JavaMail.zimbra@efficios.com>

On 2016-04-28 12:16, Michael Jeanson wrote:
> ----- On Apr 27, 2016, at 11:04 PM, Simon Marchi 
> simon.marchi at polymtl.ca wrote:
> 
>> On 2016-04-27 22:52, Simon Marchi wrote:
>>> Since these files are generated by autoconf, they shouldn't be 
>>> included
>>> in SCRIPT_LIST, which is the list of scripts to copy from the source
>>> directory to the build directory.  This gets rid of these warnings 
>>> when
>>> building:
>>> 
>>>   cp: cannot stat
>>> '/home/simark/src/babeltrace/tests/lib/test_seek_big_trace': No such
>>> file or directory
>>>   cp: cannot stat
>>> '/home/simark/src/babeltrace/tests/lib/test_seek_empty_packet': No
>>> such file or directory
>>> 
>>> Signed-off-by: Simon Marchi <simon.marchi at polymtl.ca>
>>> ---
>>>  tests/lib/Makefile.am | 4 +---
>>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>> 
>>> diff --git a/tests/lib/Makefile.am b/tests/lib/Makefile.am
>>> index e23bcc1..a08cbf6 100644
>>> --- a/tests/lib/Makefile.am
>>> +++ b/tests/lib/Makefile.am
>>> @@ -41,9 +41,7 @@ test_bt_values_SOURCES = test_bt_values.c
>>>  test_ctf_ir_ref_SOURCES = test_ctf_ir_ref.c
>>>  test_bt_ctf_field_type_validation_SOURCES =
>>> test_bt_ctf_field_type_validation.c
>>> 
>>> -SCRIPT_LIST = test_seek_big_trace \
>>> -	test_seek_empty_packet \
>>> -	test_ctf_writer_complete
>>> +SCRIPT_LIST = test_ctf_writer_complete
>>>  EXTRA_DIST = test_seek_big_trace.in test_seek_empty_packet.in
>>>  CLEANFILES= test_seek_big_trace test_seek_empty_packet
>> 
>> Sorry, forgot to mention that this series is meant for babeltrace.
> 
> Good catch, I reviewed the patches and I'm working on an updated
> version to do further cleanup of the Makefile and test scripts
> generation.

Ok thanks.

Just an idea: I find it quite cumbersome to add a new entry in 
configure.ac for each test script that we want autoconf to process (such 
as in patch 3/3).  I think it could be easier to have a single file 
(e.g. vars.sh) and have it contain definitions of various directories:

   srcdir=@srcdir@
   top_srcdir=@top_srcdir@
   abs_top_srcdir=@abs_top_srcdir@
   builddir=@builddir@
   ...

This way, you could have only a single generated file (vars.sh.in -> 
vars.sh), and each test script would just have to source that file to 
use the values.


  reply	other threads:[~2016-04-28 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  2:52 Simon Marchi
2016-04-28  2:52 ` [lttng-dev] [PATCH 2/3] tests/lib/Makefile.am: use DISTCLEANFILES instead of CLEANFILES Simon Marchi
2016-04-28  2:52 ` [lttng-dev] [PATCH 3/3] tests/lib: Make test_dwarf and test_bin_info tests work out-of-tree Simon Marchi
2016-04-28  3:04 ` [lttng-dev] [PATCH 1/3] tests/lib/Makefile.am: Remove test_seek_empty_packet and test_seek_big_trace from SCRIPT_LIST Simon Marchi
2016-04-28 16:16   ` Michael Jeanson
2016-04-28 16:44     ` Simon Marchi [this message]
2016-04-28 17:53       ` Jérémie Galarneau
2016-04-28 18:28       ` Michael Jeanson
2016-04-28 18:36         ` Simon Marchi

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=1d03bf34bd523c31ab8d32e7abda56ec@simark.ca \
    --to=simon.marchi@polymtl.ca \
    /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