Files Attributes information
| path | For category="header" the path attribute explicitly can be used to specify the include path to be added to the commandline of the build tools, specifying an imcomplete path. This way the include file requires the specification of the subdirectory (e.g. #include "sub_dir/includeFile.h") which can act as acting as namespace for header files which otherwise have the same name. |
| category | Defines the purpose of the file. Select a predefined value in the list. |
| attr | Defines the special use and handling of a file. Select a predefined value in the list ( see table below ) |
| condition | Select the identifier (attribute id) of a condition. The element is used if the condition resolves to true. If the condition resolves to false, then the element will be ignored. For example, a library might be specific for a certain toolchain or processor instruction set. |
| select | Brief description and purpose of the file. The select attribute is required when attr is set to template. When multiple template files of a component have the same select string, they are treated as a single selectable template. This way, multiple template or interface files can be bundled. |
| src | Path information. The path is specified relative to the Pack Description File. If category is set to library, then the src string can contain a list of directory paths separated by semicolons. A debugger will search those paths for locating the source files of the modules archived in the library supporting the debugging of library code. |
| version | File-specific version information. This is used particularly for
files copied into the project workspace. Before a file gets copied,
a version check avoids unnecessary copy actions. If a file does not
have a version, then the component version is used. Format : MAJOR.MINOR.PATCH[-Pre Release][+Build Metadata] |
| public | Set publishing permissions for the documentation. If |
attr
The file attribute defines the special handling in the project when being used as configuration, template, or interface file. The table lists the values available as a file attribute.
| config | The file is a configuration file of the component. It is expected that only configuration options are modified. The file is managed as part of the component, as a project-specific file typically copied into the component section of the project. |
| template | The file is used as a source code template file. It is expected to be edited and extended by the software developer. The file can be copied into a user section of the project. |