Hi,
Is there any public policy or specification for software components and/or codecs?
For example, I would to know the expected/suggested algorithm for generating of #_##_##_## format version numbers for a new codec...
Best regards,
Peter
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
Is there any public policy or specification for software components and/or codecs?
For example, I would to know the expected/suggested algorithm for generating of #_##_##_## format version numbers for a new codec...
Best regards,
Peter
Peter,
Not sure if you originally posted this in the Codecs forum, but the software products that TI releases definitely adhere to version numbering schemes. Unfortunately, I can't say that every software product that is released by every group adheres to the exact same standard, but in general they follow a AA.BB.CC.DD format in which DD is the build number, CC is used to denote patch releases, BB for minor versions and AA for major version.
Our Target Content releases (SYS/BIOS, Multimedia Frameworks, XDCTools, etc.) are uniformly versioned. All of these Target Content products (and others) adhere to the RTSC standard and you can read more about the RTSC versioning standard scheme at:
http://rtsc.eclipse.org/mediawiki-3.16/index.php?title=RTSC_Packaging_Primer/Lesson_9&redirect=no ?
Hopes this helps.
Dave
Dave,
Thank you for your useful answer, this is what I wanted to know.
Otherwise, I have another question about version numbering of TI's codec packages.
Although, all codec packages have valid and relevant version number in the package's folder name (e.g. dm6446_h264enc_2_00_01_00_production), all codec package (what I have ever seen) has [1, 0, 0] version number in the package.xdc.
Or, Is not necessary to use correct version number in package.xdc? (e.g. when I create a new XDM algorithm)
Peter
Peter,
the "[1,0,0]" is not actually a version number, but rather a compatibility key. You can read an explanation about this here. In general, you should not have to worry about this.
Dave