On Tue, Nov 19, 2013 at 6:08 PM, Gerken, Stephen < [email protected]> wrote:
> Hi all, > > > Are you looking for dependency chains from a web api down to hardware > level? > > Ideally, yes, although getting that's increasingly looking like an > unrealistic goal; for example, tizen.bluetooth > (libwrt-plugins-tizen-bluetooth-impl.so) has build dependency chains like: > tizen.bluetooth -> capi-network-bluetooth -> bluetooth-api -> > syspopup-caller -> aul -> rua -> db-util -> sqlite3 > and that's not even into the kernel yet. Just getting dependencies > understood to the level of upstream sources looks like a significant > undertaking all by itself. > Visualizing the dependencies would be great indeed. However, there's no officially supported tool at the moment. This might be interesting though https://lists.tizen.org/pipermail/ivi/2013-July/000653.html > Interestingly, tizen.bluetooth doesn't have a direct dependency on bluez; > is that interaction via dbus? > capi-network-bluetooth -> bluetooth-frwk -> bluez. -- Mikko
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
