The UDI runtime environment provides three utilities to:
These are explained in the sections below.
The udisetup utility installs a UDI driver packaged with udimkpkg on its intended target system. This utility extracts driver files from the UDI package file, installs them in environment-specific locations, and prepares the driver for use on the target system.
For syntax and usage, see udisetup(1M).
This Feature Supplement includes a utility called udibuild which builds driver modules from source files according to the build rules set in the udiprops.txt static properties file. This command is typically run from a source file directory, or run by udisetup to build a source distributed driver.
For syntax and usage information, see udibuild(1).
The udimkpkg utility is included in the UDI build environment of this Feature Supplement. udimkpkg uses the static driver properties file udiprops.txt to find various pieces of a UDI driver or library component and gathers them into a UDI package directory structure ready for distribution or installation. This command is run from the directory in which the source files are kept. It parses the udiprops.txt file contained in that directory and creates UDI packaging in directory format in a new directory, udi-pkg.1, also in the current directory.
Depending on what user id is used when udimkpkg was run to create the UDI driver, warning messages like these may be displayed while using udisetup to install the package:
UX: cpio: WARNING: Cannot get passwd information for someuser UX: cpio: WARNING: udi-pkg.1/drv/alt/comp: owner not changed UX: cpio: WARNING: Cannot get group information for someuser UX: cpio: WARNING: udi-pkg.1/drv/alt/comp: group not changed
To avoid this problem from showing up during udisetup, it is suggested (but not mandatory) that you run udimkpkg as root for the final packaging of the UDI driver during development.
For further syntax and usage information, see udimkpkg(1).