to clearly identify the API header files of a component. This could be achievable with the file category "header", but lwIP has many different header files, each describing a different type of API, i.e. udp.h, sockets.h, etc. Not every header files is a user facing API. An attribute brief or a child element <description> may solve the problem to understand the purpose of the header file(s).
The API header files are in a sub-directory, lwip and the software component itself expects this directory structure. While it is possible to define an "path" for file category "header", this is not used in this pack; perhaps because examples are missing.
The pack https://github.com/Open-CMSIS-Pack/lwIP highlights a weakness. It is currently impossible:
to clearly identify the API header files of a component. This could be achievable with the file category "header", but lwIP has many different header files, each describing a different type of API, i.e.
udp.h,sockets.h, etc. Not every header files is a user facing API. An attributebriefor a child element<description>may solve the problem to understand the purpose of the header file(s).The API header files are in a sub-directory,
lwipand the software component itself expects this directory structure. While it is possible to define an "path" for file category "header", this is not used in this pack; perhaps because examples are missing.See also: #260