udibuild(C)

udibuild -- Build UDI driver modules from source files

Synopsis

udibuild options

Description

udibuild builds driver modules from source files. udibuild is typically run from a source file directory, or run by udisetup(ADM) to build a source-distributed driver. Invoked with no command-line options, udibuild searches the current directory for a udiprops.txt file and source files, then attempts to build a driver binary using the build rules from udiprops.txt. The resultant binary object modules are placed in the bin/abi subdirectory of the current directory (creating subdirectories as needed) where the name for the current applications binary interface (ABI) is substituted for abi.

The following command-line options are understood:

-D: Specify a debug build.
-h: Display the help message.
-H: Display the full usage information.
-n: Do a dry run of udibuild. Used with the -v option, commands are not executed. Commands are echoed only.
-o dir: Specify an alternate output directory dir. By default, udibuild places one relocatable file in the current directory for each module declaration in the udiprops.txt file.
-O: Specify an optimized build. -O cannot be used with the -D option.
-s: Specify an alternate static properties file.
-T dir: Specify a temporary directory dir for udibuild to use. By default, this directory is /tmp.
-u: Build only objects whose source has changed.
-v: Specify verbose output.
-?: Display the help message.

References

udimkpkg(C) udisetup(ADM)