<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - meson incorrectly handles/reports libdrm_$foo" href="https://bugs.freedesktop.org/show_bug.cgi?id=109062#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - meson incorrectly handles/reports libdrm_$foo" href="https://bugs.freedesktop.org/show_bug.cgi?id=109062">bug 109062</a> from <a class="email" href="mailto:baker.dylan.c@gmail.com" title="Dylan Baker <baker.dylan.c@gmail.com>"> Dylan Baker</a> <pre>tl;dr: that only works if you can *always know* that you wont need a fallback and that the only way to discover all of the dependencies is via pkg-config and not via cmake or a *-config tool. imagine you have something like this: dep1 = dependency('foo', version : ['>= 1.0', '< 2.0'], fallback : ['foo', 'dep_foo']) dep2 = dependency('bar', version : '> 2.1', fallback : ['bar', 'dep_bar']) deps = [dep1, dep2] Which says, find foo and bar, and if you can't find them (and fallbacks aren't disabled) build subproject foo and get the declare_dependency object dep_foo and return that, and do the same for bar. Now, we could probably write this as: deps = dependency(['foo', 'bar'], version : [['>= 1.0', '< 2.0'], '> 2.1'], fallback : [['foo', 'dep_foo'], ['bar', 'dep_bar']]) but that's a pretty confusing syntax, and if pkg-config fails then we still have to either re-run it once for each dependency and put all of that together, or parse the human readable output and try to figure out which dependencies were missing, and rerun with on the the ones that were found and then fallback to the rest. The imagine that bar only provides a BarConfig.CMake file, or that bar provides both cmake and pkg-config, or that it only provides a bar-config script.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>