XJPack Files
An XJPack file is a container file that holds all the files for an XJTAG project, allowing a set of files to be easily deployed. Once created the XJPack file cannot be modified, providing a guarantee that the code is not modified between development and production.
Creation
XJPack files can be created from within XJDeveloper and using the command-line XJPack utility.
Versioning
XJPack files may contain a version number that is displayed alongside the project name in the XJRunner title bar. This number is set in XJDeveloper or on the XJPack command line. Alternatively, if the auto-increment option is set, then the number will get automatically updated each time the pack file is built.
The version number can be any string format that you want - it does not have to be numeric. If the auto-increment option is set, the rightmost number found in the string is incremented. For example:
| Version | Incremented |
|---|---|
| 1 | 2 |
| 1.2 | 1.3 |
| X5f | X6f |
The version is configured on the XJPack project management tab on the XJRunner Setup screen in XJDeveloper, or when exporting an XJPack file in XJDeveloper. It is exposed to XJEase XJPACK_PROJECT_VERSION.
XJTAG Target Version
XJPack files may have a preferred XJTAG target version set. A specific XJTAG release (e.g. 4.2.1) or a family of releases (e.g. 4.2) may be specified. When opening the file in any XJTAG application the user will be warned if the set target version does not match the current application version. An additional Enforce preferred target in XJIntegration option determines the behaviour in XJIntegration. If this option is enabled then the target requirement is strictly enforced, preventing the XJPack file from being opened unless the target versions matches the current XJTAG version. If this is disabled then the target version is not checked when opening the file.
The XJTAG target version is configured on the XJPack project management tab on the XJRunner Setup screen in XJDeveloper, or when exporting an XJPack file in XJDeveloper.
Accessing files from XJEase
XJEase code can read from files inside XJPack files; FOPEN first looks in the XJPack file and then to the file system when opening a file. However, files opened from inside the pack file cannot be modified; if you attempt to open a file with write or append access then FOPEN will fail and FERROR will return true. Any file that you want to include with a project, e.g. firmware files, etc, can be manually added to the XJPack file when it is created.
Note that the XJEase SYSTEM function cannot access programs or scripts stored inside the XJPack file.
XJTAG v4.2.0
