VisiBroker for .NET Developer’s Guide : Compiler options

Compiler options
This chapter describes the options you can use with the VisiBroker for .NET compilers.
Options are processed in order from left to right, giving the last value precedence. All the options in the list are enabled by default.
Options are preceded by a hyphen (-). For some of the options you can use the inverse of the default value by either using -[no_] or removing the hyphen. For example, to display a “warning” if a #pragma is not recognized, the default value is:
warn_unrecognized_pragmas
To turn off the default, type the following command:
-no_warn_unrecognized_pragmas
idl2cs[j]
The idl2cs tool compiles an IDL source file and creates a directory structure containing the C# mappings for the IDL declarations. The idl2cs and idl2csj tools are identical except that idl2csj will run in a Java-only environment (allowing the compiler to be run on platforms without .NET, including Unix and older Windows machines), while idl2cs will run in a C#-only (.NET Framework) environment.
One IDL file maps to one C# file. The default output filename for Foo.idl is Foo.cs. The output file can be specified using the -o option. Typically IDL file names must end with the .idl extension.
Syntax
idl2cs [options] {source_file}
Example
idl2cs -no_Object_method Example.idl
Defines a preprocessor macro foo, optionally with a value bar. You can use this option more than once.
Creates builtin type ::TypeCode or ::Principal. The default is on.
Generates the bind() code. The default is off.
Generates all methods on Object. The default is on.
java2cs
This command generates C# code from a Java class. java2cs translates a remote interface defined in Java RMI into corresponding C#. It will translate remote interfaces, EJB interfaces, and value classes into C#. Note that java2cs will also translate types referred to directly or indirectly by the input types.
You can use more than one Java class name (in Java byte code) as input. If you enter more than one class name, make sure you include spaces in between the class names. Use fully scoped class names. You can also provide an EJB JAR or EAR or any library JAR as input.
Note
The java2cs compiler does not support overloaded methods on CORBA interfaces.
If you use a class that extends org.omg.CORBA.IDLEntity in some Java remote interface definition, it must have the following:
an IDL file that contains the IDL definition for that type because the org.omg.CORBA.IDLEntity interface is a signature interface that marks all IDL data types mapped to Java.
If you use a class that extends org.omg.CORBA.IDLEntity in some Java remote interface definition, use the -import <IDL files> directive in the java2cs tool's command line.
For more information, refer to the CORBA 2.4 IDL2Java Specification located at http://www.omg.org.
Syntax
java2cs [options] {input_class_name}
Example
java2cs -no_tie Account Client Server
Use java2cs if you have existing Java byte code that you wish to adapt to use distributed objects or if you do not want to write IDL. By using java2cs, you can generate the necessary container classes, client stubs, and server skeletons from Java byte code.
Defines a preprocessor macro foo, optionally with a value bar.
Creates builtin type ::TypeCode or ::Principal. The default is on.
Generates tie classes. The default is on.
Generates the bind() code. The default is off.
Generates all methods defined in java.lang.Object methods, such as string and equals. The default is on.