You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 text was updated successfully, but these errors were encountered:
ReinhardKeil
changed the title
SW DATASHEET: Weakness: How to identify Provided Interfaces (API header files) of SW components
PACK DATASHEET: Weakness: How to identify Provided Interfaces (API header files) of SW components
Oct 24, 2023
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 attributebrief
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.See also: #260
The text was updated successfully, but these errors were encountered: