On 04.12.2025 13:37, [email protected] wrote: > From: Denis Mukhin <[email protected]> > > Add new make fragment for unit tests with auto-generated test harness > dependencies.
Why is this (going to be) useful? And what exactly does "auto-generated" refer to here? Not ... > --- /dev/null > +++ b/tools/Tests.mk > @@ -0,0 +1,34 @@ > +# SPDX-License-Identifier: GPL-2.0-only > +# > +# Unit test fragment. > +# > +# Copyright 2025 Ford Motor Company > + > +define list-c-headers > +$(shell sed -n \ > + 's/^[ \t]*# *include[ \t]*[<"]\([^">]*\)[">].*/\1/p' $(1) 2>/dev/null) > +endef ... the use of this construct, I suppose? When we talk of auto-generated dependencies, we normally mean what the compiler can be told to produce via -MMD. If you want such, why would you introduce (and now generalize) a fragile, custom alternative? (Fragile because afaict transitively included headers wouldn't be accounted for. Jan
