Next Previous Up Top Contents Index

7.4 The role of spec files in IDL compilation

7.4.5 Other keywords for CORBA spec files

The following keywords control other aspects of IDL compilation.

directory: directory

By default the IDL compiler puts the Dylan projects it generates into subdirectories/subfolders in the same directory/folder as the IDL source file. You can force it to put the subdirectories/subfolders in another elsewhere using this option.
The directory can be an absolute or relative name. Relative names are resolved with respect to the directory/folder the spec file is in.
prefix: directory-prefix

The default names for the generated subdirectories/subfolders are protocol, stubs and skeletons.
You can specify a prefix for these names with this prefix: option. The prefix will be appended with a leading "-" character.
This might be useful when you want to put the project subdirectories/subfolders from more than one IDL file in a common location.
idprefix: prefix-string

Though the IDL compiler now supports #pragma directives, this option, designed as a substitute for the prefix pragma directive, remains available. It sets the prefix for generated repository IDs as if the first line of the IDL file were:
#pragma prefix prefix-string
include: directory

Adds directory to the search path list which the preprocessor uses to find files mentioned in #include directives.
The directory can be an absolute or relative name. Relative names are resolved with respect to the directory/folder the spec file is in.
case: yes | no

By default the IDL compiler ignores case when recognising keywords and identifiers, but when this option is set to yes, the characters in identifiers and keywords must have exactly the same case as the identifier or keyword definition in order to be recognized.
Default value: no.
clean: yes | no

If yes, forces the IDL compiler to regenerate code irrespective of whether or not it thinks any generated code that exists is up to date with respect to the IDL source file.
Default value: no.
protocol: yes | no

If yes, this option will ensure the IDL compiler generates the protocol library from the IDL source. The protocol project will be added as a subproject of the CORBA project. This option should be used by projects that wish to use the Dylan framework generated from the IDL source but not the stubs or skeletons code.
Default value: no.

Developing Component Software with CORBA - 26 May 1999

Next Previous Up Top Contents Index