Expose API interfaces

[ReinhardKeil]

The lwIP pack seems not to define the header files that expose the actual API interface. I would have expected that 'socket.h' is exposed.

Came across this issue as we try to define "datasheets" for software components.

[RobertRostohar]

lwIP has a lot of headers that define various APIs (sockets, tcp, udp, dhcp, icmp, ...).

The pack registers the include directory rather than exposing all individual header files:
<file category="include" name="lwip/src/include/"/>

Note that lwIP source code and application code include the headers with the lwip directory prefix:
#include "lwip/tcp.h"

Therfore it is necessary to register the top level lwip/src/include directory as the include path.

[ReinhardKeil]

@RobertRostohar thanks for explaining the problem. No change to the PDSC file for now. We need to solve it differently.

[ReinhardKeil]

@jkrech could you check if it is possible to define 'lwip/tcp.h' as filename. As lwIP has many different API headers, we may need to add a "note" attribute that could supply additional information.

[jkrech]

  <file category="header" name="lwip/src/include/lwip/tcp.h" path="lwip/src/include/" />

The path attribute overrides the include path for the compiler to: -I lwip/src/include/

For the include statement this means the user needs to specify: #include "lwip/tcp.h"
(name minus path)