Skip to content

mbed-mesh-api introduces too many dependencies #14

@bremoran

Description

@bremoran

The socket abstraction layer should not introduce any dependencies which are not critical to implementing a socket API. Currently, mbed-net-socket-abstract has a target dependency on mbed-mesh-api, which introduces this tree:

mbed-mesh-api 0.0.2 yotta_modules/mbed-mesh-api
      ┣─ mbed-6lowpan 0.0.13 yotta_modules/mbed-6lowpan
      ┃ ┣─ mbed-client-c 0.1.6 yotta_modules/mbed-client-c
      ┃ ┣─ coap-service 0.0.6 yotta_modules/coap-service
      ┃ ┣─ mbed-6lowpan-eventloop 0.0.11 yotta_modules/mbed-6lowpan-eventloop
      ┃ ┃ ┗─ mbed-6lowpan-eventloop-adaptor 0.0.14 yotta_modules/mbed-6lowpan-eventloop-adaptor
      ┃ ┣─ mbed-client-randlib 0.0.2 yotta_modules/mbed-client-randlib
      ┃ ┣─ libx509-v3 0.0.2 yotta_modules/libx509-v3
      ┃ ┗─ mbed-client-ecc 0.0.2 yotta_modules/mbed-client-ecc
      ┣─ mbed-6lowpan-adaptor 0.1.0 yotta_modules/mbed-6lowpan-adaptor
      ┗─ mbed-client-libservice 3.0.1 yotta_modules/mbed-client-libservice

The socket abstraction layer should not require coap, mbed-client, ecc support, libx509, etc.

Maybe mbed-6lowpan-adaptor would be a better target dependency for mbed-net-socket-abstract.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions