From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/3] make: Add make check{,-c,-shell} targets
Date: Fri, 4 Jun 2021 18:56:00 +0200 [thread overview]
Message-ID: <YLpbIO3JlTucspgH@pevik> (raw)
In-Reply-To: <YLo9YXWrWweICm81@yuki>
Hi Cyril,
...
> > +++ b/include/mk/generic_trunk_target.inc
> > @@ -48,7 +48,7 @@
> > include $(top_srcdir)/include/mk/functions.mk
> > -RECURSIVE_TARGETS ?= all install
> > +RECURSIVE_TARGETS ?= all check check-c check-shell install
> If you add a target to RECURSIVE_TARGETS such target automatically
> traverses directories, that what the target is for. See the rule at the
> end of the generic_trunk_target.inc. Which means that you redefine
> targets if you define the same targets to loop and run the tests above.
Ah, thanks!
> I guess that you want add another target that depends on check targets
> to actually run the tests?
> Maybe:
> check-c: check-c-run
> check-c-run: $(TEST_TARGETS)
> for i in $(TEST_TARGETS); do
> ...
> done
> in order to run the tests.
> In this case the check* targets would be used for directory traversal
> and the check-c-run would be used to run the tests.
Sounds reasonable.
> > $(eval $(get_make_dirs))
> > @@ -71,7 +71,7 @@ trunk-install: $(INSTALL_FILES)
> > # Avoid creating duplicate .PHONY references to all, clean, and install. IIRC,
> > # I've seen some indeterministic behavior when one does this in the past with
> > # GNU Make...
> > -.PHONY: $(filter-out $(RECURSIVE_TARGETS),all clean install)
> > +.PHONY: $(filter-out $(RECURSIVE_TARGETS),all check clean install)
> The check is already in RECURSIVE_TARGETS
Thanks!
I'll send v2 on Monday, which also use test* as target name instead of check*
as we agreed on Richie's Libclang based analyzer patchset [1].
Kind regards,
Petr
[1] https://lists.linux.it/pipermail/ltp/2021-June/023008.html
next prev parent reply other threads:[~2021-06-04 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 18:38 [LTP] [RFC PATCH 0/3] build: make check target Petr Vorel
2021-06-03 18:38 ` [LTP] [RFC PATCH 1/3] make: Add make check{,-c,-shell} targets Petr Vorel
2021-06-04 14:49 ` Cyril Hrubis
2021-06-04 16:56 ` Petr Vorel [this message]
2021-06-04 18:01 ` Enji Cooper
2021-06-04 18:49 ` Petr Vorel
2021-06-03 18:38 ` [LTP] [RFC PATCH 2/3] build.sh: Add support for make check Petr Vorel
2021-06-03 18:38 ` [LTP] [RFC PATCH 3/3] CI: Run also " Petr Vorel
2021-06-04 14:43 ` [LTP] [RFC PATCH 0/3] build: make check target Richard Palethorpe
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=YLpbIO3JlTucspgH@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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