tree c12cafdf3773cfc2d58165ce8bbcb4a1f57fdb80
parent 1d7b4788943d5450e2c72965bb972369ae908b2c
author Andrew Jeffery <andrew@codeconstruct.com.au> 1704335716 +1030
committer Andrew Jeffery <andrew@codeconstruct.com.au> 1705024135 +0000

meson: Order dependencies as an approximate in-order tree traversal

meson appears to not be terribly fancy about resolving dependency
constraints. Dependencies appear to be evaluated in their order of
declaration, as an in-order tree traversal. This ordering is problematic
for escalating version constraints.

As a concrete example, we currently declare `dependency('sdbusplus')`
before `dependency('boost')`. sdbusplus itself depends on boost, without
a version constraint. If boost is available on the build system then
this is selected. However, dbus-sensors' boost dependency may have a
version constraint of e.g. >=1.83.0. In this arrangement we hit the the
following error:

```
sdbusplus| Run-time dependency Boost found: YES 1.81.0 (/usr/include)
...
Dependency boost found: NO found 1.81.0 but need: '>=1.83.0' (cached)

meson.build:67:8: ERROR: Dependency 'boost' is required but not found.
```

Declare (common) dependencies as an approximate in-order traversal to
avoid conflicts.

Change-Id: I0277061f3ac36361495183018293a61163d70a36
Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>