Create a tar file containing a filesystem for a specified board variant
mktar [-o output] [options] ... [board_name_argument]
QNX Neutrino
If you specify both the -p and -m options, any intermediate directories you have created have mode u+wx.
The mktar utility creates a tar file containing the filesets listed in the board-specific profile, resulting in proper ownership and permissions. Don't use mktar on its own to create a tar file. Instead, use the mksysimage.py Python script, with the --no-mkimage option to create .tar files and no image.
The mktar utility creates a tar file containing the filesystem for a specified variant, typically used by mksysimage.py to include in the resulting image that's generated. It currently requires binary content from your installed software as well as source and deployment files.
Before you can use this utility, you must have the following prerequisites:
skipped missing item: lib/firmware/vpu/vpu_fw_imx6q.bin
The mktar uses Python's tarfile module to generate a tar file with the appropriate permissions. The list of included files is determined by a board profile, which is stored as profile.xml in the board directory (e.g., %QNX_CAR_DEPLOYMENT%/boards/omap5uevm.car2/profile.xml). For more information and for details about dependencies, see the file located at %QNX_TARGET%/pymodules/qnxcar/config.py.
You can overwrite the default profile by using the --profile option.
The mktar utility with the -vvv option will show the search path used to find files. The typical search path (implemented in deployment/pymodules/qnxcar/path.py:get_stage_locator) is as follows:
Overriding files to create custom mktar images
The mktar utility will search the search paths identified above to find all files defined in a particular board's profile.xml file. To include a new version of any file (e.g., a driver, configuration file, etc.), you would copy the file into the appropriate search path, and then rerun mktar.
To choose the appropriate search path, you need to determine the following:
To create a tar file for OMAP5432:
%QNX_TARGET%/scripts/mktar -o omap5uevm_external.tar
omap5uevm.external
This command creates a file named omap5uevm_external.tar that contains the QNX CAR filesystem for the OMAP5432 board.
To create a tar file for SABRE Lite:
%QNX_TARGET%/scripts/mktar -o imx61sabre_external.tar
imx61sabre.external
This command creates a file named imx61sabre_external.tar that contains the QNX CAR filesystem for SABRE Lite. To list all available platform.variant pairs, you can run:
ls -d %QNX_CAR_DEPLOYMENT%/boards/*.*
The output is compressed if the filename in the mktar command ends with .gz or .bz2. The utility can also be used without a board configuration, by manually specifying filesets (and a CPU type if applicable). You can also add extra filesets to a board's default configuration.
None.