Texas Instruments TMS320 DSP User Manual
Page 36
www.ti.com
Packaging
If multiple versions of the same component are provided by a single vendor, the different versions must be
in different libraries (as described above) and these libraries must be named as follows:
<module><vers>_<vendor>_<variant>.1<arch>
where <variant> is the name of the variant of the module (containing characters from the set[a-z0-9]).
Debug variants should have variant names that begin with the characters "debug." If there is only one
release version of a component from a vendor, there is no need to add a variant suffix to the library name.
Suppose, for example, that TI supplies one debug and one release version of the FIR module for the
C62xx architecture. In this case, the library file names would be "fir_ti_debug.l62" and "fir_ti.l62".
To avoid having to make changes to source Code, only one header file must suffice for all variants
supplied by a vendor. Since different algorithm implementations can be interchanged without recompilation
of client programs, it should not be necessary to have different "debug" versus "release" definitions in a
module's header. However, a vendor may elect to include vendor specific extensions that do require
recompilation. In this case, the header should assume that the symbol _DEBUG is defined for debug
compilations and not defined for release compilations.
Rule 18
If a module’s header includes definitions specific to a “debug” variant, it must use the symbol _DEBUG
to select the appropriate definitions. _DEBUG is defined for debug compilations and only for debug
compilations.
Algorithm Component Model
36
SPRU352G – June 2005 – Revised February 2007