Commands
Four different operations require the generation of an abstract command:
For each operation, a template command is shown, followed by a description of each value in the command with its origin.
Compiling
<comp_prog> OP <operation> IF <input_file> OF <output_file>
IN <include_dir> FL <comp_flags…> ::
where comp_prog and comp_flags come from preferences, while the remaining options are generated by Riverbed Modeler. The value of operation is comp_so if the object code must be relocatable (if it is to go into a shared object), or comp if the object code does not need to be relocatable. Information about this command is listed in the following table.
Table 24: Compile Command Options
| Component | Description |
|---|---|
| comp_prog | The name of the ECI translator which will generate a command or commands to compile the input file to the output file. |
| operation | One of comp or comp_so. |
| input_file | The name of the source file to compile. |
| output_file | The name of the destination object file. |
| include_dir | The name of an include directory to add to the include path of the compiler. |
| comp_flags | User-specified flags to pass on to the compiler. |
Binding Executables
<bind_static_prog> OP bind IF <input_file> OF <output_file>
FL <bind_static_flags> :: LB <archive> <bind_static_libs> ::
where bind_static_prog, bind_static_flags, and bind_static_libs come from preferences, and the rest are generated by Riverbed Modeler. archive is the input archive library file (i.e. the ".si.a" file). Information about this command is listed in the following table.
Table 25: Bind Executables Command Options
| Component | Description |
|---|---|
| bind_static_prog | The name of the ECI translator which will generate a command or commands to link the input file with the archive and static libraries to form an output file executable. |
| input_file | The name of the main object file to link with the archives and other libraries. |
| output_file | The name of the destination executable file. |
| bind_static_flags | User-specified flags to pass on to the linker. |
| archive | Name of archive library to include in the executable. |
| bind_static_libs | User-specified static libraries to include in the linking. |
Binding Shared Objects
<bind_shobj_prog> OP bind_so IF <input_file> OF <output_file>
XF <export_file> FL <bind_shobj_flags> :: LB <libraries> ::
where bind_shobj_prog and bind_shobj_flags come from preferences, and the rest are generated by Riverbed Modeler. The libraries are only specified under Windows, where they are necessary for generating DLLs. Here, input_file will be a response file listing the object files that will go into the shared library and export_file lists the external symbols in the library (not necessary under Linux). Information about this command is listed in the following table.
Table 26: Binding Shared Objects Command Options
| Component | Description |
|---|---|
| bind_shobj_prog | The name of the ECI translator which will generate a command or commands to link the input files with the libraries to form a shared object library. |
| input_file | The name of the response file which contains the names of object files to link into the shared library. |
| output_file | The name of the destination shared object library. |
| export_file | The name of a file listing external symbols in the library (Windows only). |
| bind_shobj_flags | User-specified flags to pass on to the linker. |
| libraries | Libraries to include in the link phase, necessary under Windows to generate shared object libraries. These libraries are specified by Riverbed Modeler. |
Archiving
<arch_prog> OP arch IF <input_file> OF <output_file>
where arch_prog is a preference. As above, input_file will be a response file. Information about this command is listed in the following table.
Table 27: Archiving Command Options
| Component | Description |
|---|---|
| arch_prog | The name of the Eci translator which will generate a command or comma to place the files listed in the input response file into a static library. |
| input_file | The name of the response file which contains the names of object files to link into the static library. |
| output_file | The name of the destination static object library. |