| ナビゲーションリンクをスキップ | |
| 印刷ビューの終了 | |
|
マニュアルページセクション 1: ユーザーコマンド Oracle Solaris 11.1 Information Library (日本語) |
| ナビゲーションリンクをスキップ | |
| 印刷ビューの終了 | |
|
|
マニュアルページセクション 1: ユーザーコマンド Oracle Solaris 11.1 Information Library (日本語) |
- code generator
/usr/bin/radadrgen [-N] spec.xml
/usr/bin/radadrgen [-N] -c dir [-r [ -m ] [ -s ]] spec.xml
/usr/bin/radadrgen [-N] -j dir [-i] spec.xml
/usr/bin/radadrgen [-N] {-o docbook | docbook-man | man | rmdoc} spec.xml/usr/bin/radadrgen -d baseline.xml spec.xml
The radadrgen command is the ADR IDL processing tool. Its primary purpose is to generate language bindings for the rad server and the various rad client environments. It can also generate documentation, and audit changes to interfaces for consistency with their versions.
All invocations validate the given spec.xml against the ADR schema.
The following options are supported:
Do not limit what types can be nullable. This restriction is in place to facilitate mapping to languages where certain types are not naturally nullable. This option relaxes this restriction for uses where it is both permissible and advantageous for all types to be nullable.
Generate C definitions for the types and interfaces defined in the input file. Files will be created under dir.
Generate C server-side definitions that reference entry points using the prescribed entry-point naming scheme.
Do not generate separate definitions for inherited interfaces. By default, new definitions are generated for inherited interfaces, replicating the definitions in the inherited interface.
Generate C stubs for entry points referenced by the definitions created by the -r option.
Generate Java interfaces for the types and interfaces defined in the input file. The Java source tree will be created under dir.
Generate concrete implementation classes for the interfaces created for structured types.
Generate documentation, in the given format, for the interface definition in spec.xml. Documentation can be improved by decorating the various parts of the interface definition with summary and doc elements.
Valid formats:
standard docbook format
man page content in docbook format, a precursor to man format, below
a man page, in [nt]roff format
spec.xml, with the summary and doc elements removed
Compare the interfaces defined by baseline.xml and spec.xml and verify that the version of the modified interface is consistent with the differences found. An error message is displayed if the versions are inconsistent.
The following operand must be specified on the command line:
The path to the API specification for which type and interface definitions must be generated.
The core ADR RelaxNG schema definition.
The ADR RelaxNG schema definition for documentation elements.
See attributes(5) for descriptions of the following attributes:
|
|