www.ti.com
Packaging
Ifmultipleversionsofthesamecomponentareprovidedbyasinglevendor,thedifferentversionsmustbe
indifferentlibraries(asdescribedabove)andtheselibrariesmustbenamedasfollows:
<module><vers>_<vendor>_<variant>.1<arch>
where<variant>isthenameofthevariantofthemodule(containingcharactersfromtheset[a-z0-9]).
Debugvariantsshouldhavevariantnamesthatbeginwiththecharacters"debug."Ifthereisonlyone
releaseversionofacomponentfromavendor,thereisnoneedtoaddavariantsuffixtothelibraryname.
Suppose,forexample,thatTIsuppliesonedebugandonereleaseversionoftheFIRmoduleforthe
C62xxarchitecture.Inthiscase,thelibraryfilenameswouldbe"fir_ti_debug.l62"and"fir_ti.l62".
ToavoidhavingtomakechangestosourceCode,onlyoneheaderfilemustsufficeforallvariants
suppliedbyavendor.Sincedifferentalgorithmimplementationscanbeinterchangedwithoutrecompilation
ofclientprograms,itshouldnotbenecessarytohavedifferent"debug"versus"release"definitionsina
module'sheader.However,avendormayelecttoincludevendorspecificextensionsthatdorequire
recompilation.Inthiscase,theheadershouldassumethatthesymbol_DEBUGisdefinedfordebug
compilationsandnotdefinedforreleasecompilations.
Rule18
Ifamodule’sheaderincludesdefinitionsspecifictoa“debug”variant,itmustusethesymbol_DEBUG
toselecttheappropriatedefinitions._DEBUGisdefinedfordebugcompilationsandonlyfordebug
compilations.
AlgorithmComponentModel 36SPRU352G–June2005–RevisedFebruary2007
SubmitDocumentationFeedback