In the build run, the keyword build is followed by a unique name that can be used to identify objects generated by the external program.
The unique name is a string of alphanumeric characters (e.g. f200),
which can be used as a name for
objects (files, traffic control elements, etc.) generated by the
external program. The name is generated such that it is unique for
this run of tcc. Consecutive runs of tcc may use the same name.
The name is short enough that it is still a valid traffic control
element identifier if the external program adds two more characters.
Note that the unique name may begin with a digit, so at least one
letter must be prepended in order to obtain a valid C identifier.
The external program is under no obligation of using the identifier provided by tcc. At the end of a build run, it returns a list of elements for the traffic control subsystem of the kernel that need to be loaded and initialized to implement the configuration, as described in section 7.3.3.
Figure 7.1 illustrates the interaction between tcc and the external program when building modules.
On standard input, tcc provides configuration data in the format described in the following section.
