On 01/02/14 20:21, Stephen Kelly wrote: > On 02/01/2014 08:22 PM, Alex Merry wrote: >> So, I think that find_dependency should pass QUIET to find_package >> whether or not the parent package is being found quietly. >> >> Do other people agree? > > I agree with the problem statement, but not the solution proposed. I > don't think finding all dependencies QUIETly makes sense. That has other > side-effects. > > Did you/will you consider changing the feature_summary implementation to > filter them out another way? How does feature summary work? Can the > find_dependency macro somehow omit entries from feature_summary? > (without affecting other direct find_package calls?
That makes sense. The obvious thing to do is set a package property (or something equivalent) that says it was found as a dependency. The danger there is that if something is first found as a dependency and then found explicitly, it will be supressed. We could minimise that by also checking that the TYPE and PURPOSE package properties were not set. Alex _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
