iip_build command
The iip_build command is used to build IIPs.
Usage
More details on parameters supplied to the iip_build script can be
found on the IIP attributes page.
Usage: ./iip_build [options]
Options:
[--help] Display this help and exit.
--name <name> Name of IIP.
--version <version> Build version.
[--branch <branch>] Branch from which IIP was built.
[--content_version <version>] Version of IIP content, such as application version.
[--date <date>] Date of build.
[--time <time>] Time of build.
[--description <file>] Description XML file.
[--toolchain <toolchain>] Name of toolchain to build the IIP for (e.g. bcm15
It is not used if the IIP works on all architectures.
[--device <device>] Device model to build the IIP for (e.g. vip43x2).
Used for IIPs meant to run only on a specific
device.
--install <type>:<script> Type of installation script (buildtime/kit)
and file which acts as installation script. Type
buildtime installs IIP in rootdisk at buildtime.
[--depends <type>:<IIP name>] Type of dependency (rootdisk/finalize/kit) and
name of IIP on which this IIP depends on.
Type rootdisk is used for regular IIPs.
Type kit is for IIPs that should be included
when building kits but ignored when building
boot-images. Type kit is used internally at ARRIS.
[--data_dir <directory>] A directory containing directories and files to
be included in the IIP.
[--out_dir <out_dir>] Output directory in which the IIP is created,
default is current directory.
[--objcopy <script>] Script which copies debug symbols from binaries
to separate files in the data directory.
Script bin/objcopy_tree can do the job.
[--strip <script>] Script which removes debug symbols from binaries
in the data directory. Script bin/strip_tree
can do the job.
[--provides_capability [<type>:]<media_capability>]
Platform capability type and media capability.
Used for IIPs providing a capability of some
sort. The capability is exposed through TOI.