public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>, passt-dev@passt.top
Subject: Re: [PATCH v2 01/13] Makefile: Use make variables for static checker configuration
Date: Tue, 5 May 2026 12:49:11 +0200	[thread overview]
Message-ID: <945d5ad2-a900-4a43-bb80-f45e99747f20@redhat.com> (raw)
In-Reply-To: <20260505122048.2982126f@elisabeth>

On 5/5/26 12:20, Stefano Brivio wrote:
> On Tue, 5 May 2026 12:14:02 +0200
> Laurent Vivier <lvivier@redhat.com> wrote:
> 
>> On 4/21/26 05:23, David Gibson wrote:
>>> Our cppcheck and clang-tidy rules don't really follow normal Makefile
>>> conventions.  Usually any commands other than the very basics have their
>>> binary specified in a variable so it can be overridden on the command line
>>> if they're in an unusual location.  Implement that for $(CPPCHECK) and
>>> $(CLANG_TIDY)
>>>
>>> Likewise flags to tools usually have their own Make variable.  Do the same
>>> with $(CLANG_TIDY_FLAGS) and $(CPPCHECK_FLAGS).  Note that these only have
>>> the options specifically for the static checker, not compiler flags which
>>> we are also supplying to the static checker - those are derived from
>>> FLAGS / CFLAGS / CPPFLAGS as before.
>>>
>>> As part of that we change the probing for --check-level=exhaustive from
>>> being run as part of the cppcheck target, to being run when we build the
>>> CPPCHECK_FLAGS variable.  That doesn't make any real difference now, but
>>> will make things nicer if we need multiple cppcheck targets in future (e.g.
>>> for passt-repair).
>>>
>>> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>>> ---
>>>    Makefile | 32 +++++++++++++++++++-------------
>>>    1 file changed, 19 insertions(+), 13 deletions(-)
>>>
>>> diff --git a/Makefile b/Makefile
>>> index f697c12b..17e70d22 100644
>>> --- a/Makefile
>>> +++ b/Makefile
>>> @@ -174,21 +174,27 @@ docs: README.md
>>>    		done < README.md;					\
>>>    	) > README.plain.md
>>>    
>>> +CLANG_TIDY = clang-tidy
>>> +CLANG_TIDY_FLAGS = -DCLANG_TIDY_58992
>>> +
>>>    clang-tidy: $(PASST_SRCS)
>>> -	clang-tidy $^ -- $(filter-out -pie,$(FLAGS) $(CFLAGS) $(CPPFLAGS)) \
>>> -	           -DCLANG_TIDY_58992
>>> +	$(CLANG_TIDY) $^ -- $(filter-out -pie,$(FLAGS) $(CFLAGS) $(CPPFLAGS)) \
>>> +		$(CLANG_TIDY_FLAGS)
>>>    
>>> -cppcheck: $(PASST_SRCS) $(HEADERS)
>>> -	if cppcheck --check-level=exhaustive /dev/null > /dev/null 2>&1; then \
>>> -		CPPCHECK_EXHAUSTIVE="--check-level=exhaustive";		\
>>> -	else								\
>>> -		CPPCHECK_EXHAUSTIVE=;					\
>>> -	fi;								\
>>> -	cppcheck --std=c11 --error-exitcode=1 --enable=all --force	\
>>> +CPPCHECK = cppcheck
>>> +CPPCHECK_FLAGS = --std=c11 --error-exitcode=1 --enable=all --force	\
>>>    	--inconclusive --library=posix --quiet				\
>>> -	$${CPPCHECK_EXHAUSTIVE}						\
>>>    	--inline-suppr							\
>>> -	--suppress=missingIncludeSystem \
>>> +	$(shell if $(CPPCHECK) --quiet --check-level=exhaustive /dev/null; then \
>>> +		echo "--check-level=exhaustive";			\
>>> +	else								\
>>> +		echo "";						\
>>> +	fi)			
>>
>> Perhaps we can add a reusable function to check flags:
>>
>> check_flag = $(shell $(1) $(2) >/dev/null 2>&1 && echo $(2))
>>
>> Then
>> 	$(call check_flag, $(CPPCHECK) /dev/null, --check-level=exhaustive)
>> 				\
>>> +	--suppress=missingIncludeSystem					\
>>>    	--suppress=unusedStructMember					\
>>> -	$(filter -D%,$(FLAGS) $(CFLAGS) $(CPPFLAGS)) -D CPPCHECK_6936	\
>>> -	$^
>>> +	 -D CPPCHECK_6936
>>> +
>>> +cppcheck: $(PASST_SRCS) $(HEADERS)
>>> +	$(CPPCHECK) $(CPPCHECK_FLAGS) 					\
>>> +		$(filter -D%,$(FLAGS) $(CFLAGS) $(CPPFLAGS)) $^		\
>>> +		$^
>>
>> You have duplicate '$^' here.
> 
> Just note that it's not necessarily important to review this series
> right now (I'm not sure).

okay, I was reviewing it because "Dynamic configuration" series doesn't apply cleanly 
without it.

> 
> I guess if we can "fix" it (see my concerns about 4/13) quickly, then
> it's useful, and I'll try to pick it up like that (feel free to post a
> new version yourself, of course!).
> 
> But if it needs major reworks I'd rather try to come up with something
> minimal instead, for the moment.
> 

Thanks,
Laurent


  reply	other threads:[~2026-05-05 10:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  3:23 [PATCH v2 00/13] Improvements to static checker invocation David Gibson
2026-04-21  3:23 ` [PATCH v2 01/13] Makefile: Use make variables for static checker configuration David Gibson
2026-05-05 10:14   ` Laurent Vivier
2026-05-05 10:20     ` Stefano Brivio
2026-05-05 10:49       ` Laurent Vivier [this message]
2026-05-05 13:14         ` Stefano Brivio
2026-05-05 14:04     ` David Gibson
2026-04-21  3:23 ` [PATCH v2 02/13] cppcheck: Split out essential defines into a BASE_CPPFLAGS variable David Gibson
2026-05-05 10:26   ` Laurent Vivier
2026-05-06  7:46   ` Stefano Brivio
2026-05-06  8:08     ` David Gibson
2026-04-21  3:23 ` [PATCH v2 03/13] Makefile: Remove preprocessor flags from $(FLAGS) David Gibson
2026-04-21  3:23 ` [PATCH v2 04/13] Makefile: Remove non-standard $(FLAGS) variable David Gibson
2026-04-28  7:17   ` Stefano Brivio
2026-04-29  3:47     ` David Gibson
2026-04-29  5:01       ` David Gibson
2026-05-03 21:56       ` Stefano Brivio
2026-05-04  4:47         ` David Gibson
2026-05-04 23:10           ` Stefano Brivio
2026-05-05 14:24             ` David Gibson
2026-04-21  3:23 ` [PATCH v2 05/13] Makefile: Make conditional definition of $(BIN) clearer David Gibson
2026-04-21  3:23 ` [PATCH v2 06/13] Makefile: Use common binary compilation rule David Gibson
2026-04-21  3:23 ` [PATCH v2 07/13] Makefile: Remove unhelpful $(HEADERS) variable David Gibson
2026-04-21  3:23 ` [PATCH v2 08/13] Makefile: Add header dependencies for secondary binaries David Gibson
2026-04-21  3:23 ` [PATCH v2 09/13] Makefile: Split static checker targets David Gibson
2026-04-21  3:23 ` [PATCH v2 10/13] passt-repair: Split out inotify handling to its own function David Gibson
2026-04-21  3:23 ` [PATCH v2 11/13] passt-repair: Simplify construction of Unix path from inotify David Gibson
2026-04-21  3:23 ` [PATCH v2 12/13] passt-repair: Run static checkers David Gibson
2026-04-21  3:23 ` [PATCH v2 13/13] qrap: " David Gibson
2026-04-28  7:17   ` Stefano Brivio
2026-04-29  3:48     ` David Gibson

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=945d5ad2-a900-4a43-bb80-f45e99747f20@redhat.com \
    --to=lvivier@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).