cunomaker
The cunomaker generates a C representation for idl types. The cunomaker works
on a typelibrary which is generated by the unoidl. It generates the output for
all specified types and for all types the specified types depends on.
cunomaker [-options] file_1 ... file_n
Options:
- -O<path>
- path describes the root
directory for the generated output. The output directory tree is generated
under this directory.
- -T<name>
- name specifies a type
or a list of types. The output for this [t1;...] type is generated. If no
'-T' option is specified, then output for all types is generated.
- -B<name>
- name specifies the base node. All types are
searched under this node. Default is the root '/' of the registry files.
- -U activate the generating of a getCppuType function
- -C
- In general the cunomaker tool generates getCppuType_<name>()
functions in two ways.
-
- no option (default)
This generates header in the way, that UNO runs correctly as long as:
- -- one compiler
compiled all code (no bridging needed for inter component communication)
- -- no marschalling
is needed (no bridging needed for inter process communication)
- -- no scripting
is needed (in general this needs full type description support)
- -C (fully comprehensive type information)
This options generates the longest form of getCppuType_<name>()
functions, including a comprehensive description of a type, thus there
is no need for a type description manager (+provider) reading types
from applicat.rdb:
- -- limitation:
only previously used types are provided by the runtime (i.e., only
types which were previously registered due to a getCppuType() call
are accessable by name)
So please keep these limitations in mind, if you are not sure that there
is a running type description manager (+provider) reading from applicat.rdb.
- -G
- generate only target files which does not exists.
- -Gc
- generate only target files which content will
be changed.
Legal Notices