From RTSC-Pedia
 | [printable version] [offline version] | offline version generated on 04-Aug-2010 21:08 UTC |  |
XDCtools Internal Version Numbers
Managing packages built with different versions of XDCtools
Contents |
Introduction
When building a package, XDCtools adds special marker files to the package to specify the versions of different internal package files. There are four such marker files, their names end with digits marking the versions of internal files, and they are located in the subdirectory package.
- vers_gNNN
- Specifies the version of the file package/<packageName>.ccs. This file contains an internal representation of XDCspec files in the package.
- vers_rNNN
- Specifies the version of the file package/<packageName>.java. This file establishes XDCscript representations of types and objects defined in the package.
- vers_bNNN
- Specifies the version of the file package/package_<packageName>.c. This file contains the target representation of the package.
- vers_cNNN
- Specifies the version of the file package/package.doc.xml. This file is used by xdc.tools.cdoc to display the package documentation.
When XDCtools loads a package, the marker files determine if the internal files in the loaded package are compatible with XDCtools. If not, XDCtools rebuilds the incompatible internal files, and then uses the rebuilt internal files instead of ones originally delivered with the package. For example, if XDCtools 3.15 loads a package built with XDCtools 3.10, none of the version numbers will match and the internal files for that package will be rebuilt by XDCtools 3.15 before the package can be used. Rebuild of the internal files adds to the configuration time, with package/<packageName>.java files causing the largest performance impact.
If the version numbers of XDCtools match with the package's version numbers, the internal files are used as they are. That is the case when XDCtools 3.10.03 loads a package built with XDCtools 3.10.
If only one of the version numbers does not much, as is the case for XDCtools 3.10.05 and packages built with XDCtools 3.10, only the corresponding internal file package/package_<packageName>.c is rebuilt.
If a package does not have one of the marker files, either because it is built with an XDCtools release that did not create such files or the marker file was deleted, the corresponding internal file will be regenerated.
Internal version numbers of XDCtools releases
| Release | .vers_r | .vers_g | .vers_b | .vers_c |
|---|---|---|---|---|
| 2.94 | - | - | - | - |
| 2.95 | - | - | - | - |
| 2.95.01 | 100 | 101 | 100 | - |
| 2.95.02 | 100 | 101 | 100 | - |
| 3.00 | 100 | 102 | 100 | - |
| 3.00.01 | 103 | 102 | 100 | - |
| 3.00.02 | 103 | 102 | 100 | - |
| 3.00.03 | 103 | 102 | 100 | - |
| 3.00.04 | 103 | 102 | 100 | - |
| 3.00.05 | 103 | 102 | 101 | - |
| 3.00.06 | 103 | 102 | 101 | - |
| 3.05.xx | 104 | 102 | 102 | - |
| 3.10.xx | 108 | 104 | 102 | - |
| 3.15 | 150 | 150 | 150 | 150 |
| 3.15.01 | 160 | 150 | 150 | 150 |
| 3.15.02 | 160 | 150 | 150 | 150 |
| 3.15.03 | 170 | 160 | 150 | 150 |
| 3.15.04 | 170 | 160 | 150 | 150 |
| 3.16.xx | 170 | 160 | 150 | 150 |
| 3.20 | 170 | 180 | 150 | 150 |
