On Thu, Sep 28, 2023 at 3:06 PM Akhil Goyal <gak...@marvell.com> wrote: > > > Some tests make optionally use a component but don't require it for > > > > s/make // > > > > > building. If we include the dependency in the per-file lists, then tests > > > may be unnecessarily omitted, as the dependency is not required. > > > On the other hand, removing the optional dependency from the list can > > > cause build failures, as the test case may include the optional code, > > > but then fail to build as the build system won't have added the necessary > > > paths for header inclusion, or the necessary libraries for linking. > > > > > > Resolve this by explicitly providing a list of optional dependencies. > > > Any items in this list will be added to the dependency list if > > > available, but otherwise won't be involved in enable/disable of specific > > > tests. > > > > > > Signed-off-by: Bruce Richardson <bruce.richard...@intel.com> > > Reviewed-by: David Marchand <david.march...@redhat.com> > Tested-by: Akhil Goyal <gak...@marvell.com>
Series applied, thanks for the quick fix Bruce. -- David Marchand
