-
Notifications
You must be signed in to change notification settings - Fork 5
Component Definition
All COMP options are organized within the following sections:
meta | Descriptions, titles etc |
general | General settings for the COMP file. |
libraries | See special notes. |
exports | Items to be exported together with the built component are specified here. |
Notes about the [libraries] section
The libraries section is different from regular sections in the sense that it doesn’t contain the usual option/value pairs. There are no predefined options for this section.
Each option name given is interpreted as a library title. The value of the option must be a List of FString items representing the codemodules which will be included in a build to produce a library with the given libary title. For instance, imagine the below
example:
[libraries] mylib = matrix;color;vector;quat
This section will result in the given four code modules matrix, color, vector and quat to be compiled into a library called mylib.*. The library extension will be set differently depending on the compiler used. For example, building for Windows will result in mylib.lib, building for symbian target results in mylib.a and so on.
If a larger number of modules need to be specified as the source to a library, they can be listed in an external file and passed as module name prefixed with ‘@’. Imagine the following example:
[libraries] mylib = matrix;color;vector;quat;@filters.lst;@../modules.lst
The component builder will attempt to open the file ‘filters.lst’ and ‘../modules.lst’ and read them as a pure lists of code modules where each list element equals a single line of
the file.