9 Using the Dylan IDL Compiler

9.3 Code generation options

/language:name: The /language option is deprecated, but is still supported for backward compatibility. It has been replaced with the /back-end option.
/back-end:name: The /back-end option selects which back-end the compiler should use on the IDL file. Two values are supported:
: dylan - This is the default value. The Dylan back-end generates Dylan protocol, stubs and skeletons libraries.
: ir - This value causes the compiler to load the definitions in the IDL file into an Interface Repository. It will overwrite any definitions in the repository with the same scoped names. The compiler uses a call to the standard CORBA ORB operation ResolveInitialReferences to obtain a reference to the Interface Repository. Note that Functional Developer does not have its own Interface Repository, but you can use one supplied by a third party. You may use the -ORBinterface-repository-file and -ORBinterface-repository options (described in Section 8.3.4, "ORB runtime switches") to specify an object reference for ResolveInitialReferences to return.
: More than one /back-end option may be supplied if you want to load the IDL into an Interface Repository and generate Dylan code.
/parse: Parse the IDL file only. This option overrides /back-end.

The following three options only apply to the Dylan back-end.

/directory:dir: By default console-scepter.exe puts the Dylan projects it generates into subfolders in the current working folder. You can force it to put the subfolders in another folder dir by using the /directory option.
/prefix:name: The default names for the subfolders are protocol, stubs and skeletons. You may specify a prefix for these names with the /prefix option. This might be useful, for example, where you want to put the project subfolders from more than one IDL file into a common folder.
/stubs: By default console-scepter.exe generates three libraries for each IDL file: a protocol library, a stubs library, and a skeletons library. However, you may not always want to generate both the stubs and skeletons libraries. For example if you are developing a client application you will only need the stubs library. The /stubs option causes console-scepter.exe to generate only the protocol and stubs libraries.