Development
Development preferences are used in the process of developing software modules: e.g., object code files, archive-based object code libraries, or executable programs. These preferences manipulate the operating system commands that compile, archive, and bind (link). Only programs that create software modules accept these preferences, and some of these programs only accept a subset of the preferences (for instance, just the compile and archive-related preferences).
When compiling C++ code, there are several development preferences that must be set to correctly compile and link the code. Table 17 lists these preferences and their values for each operating system and compiler, depending on whether op_mksim or op_runsim is being used to create the simulation executable file.
Table 17: Compiling and Linking Program Preferences for C++
| OS | Version | Compiler | op_mksim | op_runsim |
|---|---|---|---|---|
| Linux | any | gcc | comp_prog_cpp: comp_unix_cpp or comp_g++ bind_static_prog: bind_unix or bind_g++ |
comp_prog_cpp: comp_unix_cpp or comp_g++ bind_shobj_prog: bind_so_unix or bind_so_g++ |
| Windows | 2000, XP | Visual C++ | comp_prog_cpp: comp_msvc bind_static_prog: bind_msvc |
comp_prog_cpp: comp_msvc bind_shobj_prog: bind_so_msvc |
bind_shobj_flags
Specifies flags to be passed to the “binder” program when creating a shared object.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_flags_32bit
Specifies flags to be passed to the “binder” program when creating a shared object for a 32-bit simulation kernel or ETS library.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_flags_64bit
Specifies flags to be passed to the “binder” program when creating a shared object for a 64-bit simulation kernel or ETS library.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_flags_devel
Specifies flags to be passed to the “binder” program when creating a shared object for a development simulation kernel or ETS library.
| Data Type | Default Value |
|---|---|
| string | Windows: “/DEBUG” Linux: “” |
bind_shobj_flags_optim
Specifies flags to be passed to the “binder” program when creating a shared object for an optimized simulation kernel.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_libs
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into a network repository or library). The binder program is indirectly invoked through the ECI program specified by the bind_shobj_prog preference. The value of bind_shobj_libs should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_libs_32bit
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into a network repository or library) for use with a 32-bit simulation kernel or a 32-bit application. The binder program is indirectly invoked through the ECI program specified by the bind_shobj_prog preference. The value of bind_shobj_libs_32bit should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_libs_64bit
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into a network repository or library) for use with a 64-bit simulation kernel or a 64-bit application. The binder program is indirectly invoked through the ECI program specified by the bind_shobj_prog preference. The value of bind_shobj_libs_64bit should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_libs_devel
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into a network repository or library) for use with a development simulation kernel or an application. The binder program is indirectly invoked through the ECI program specified by the bind_shobj_prog preference. The value of bind_shobj_libs_devel should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_libs_optim
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into a network repository or library) for use with an optimized simulation kernel or an application. The binder program is indirectly invoked through the ECI program specified by the bind_shobj_prog preference. The value of bind_shobj_libs_optim should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_shobj_prog
Specifies the ECI translation program or script to invoke to create a shared object library.
| Data Type | Default Value |
|---|---|
| string | Windows: bind_so_msvc Linux: bind_so_unix |
| Built-in Scripts (Windows) | - bind_so_msvc – use Microsoft Visual Studio C/C++ linker |
| Built-in Scripts (Linux | - bind_so_cc – link shared library with gcc linker - bind_so_gcc – link shared library with gcc linker - bind_so_g++ – link shared library that contains C++ code with gcc linker - bind_so_unix – use default for architecture (equivalent to bind_so_g++ on Linux) |
bind_static_flags
Specifies optional flags to be passed to the “binder” program when creating a static executable.
| Data Type | Default Value |
|---|---|
| string | Windows: “/link /LARGEADDRESSAWARE” Linux: “” |
bind_static_flags_32bit
Specifies optional flags to be passed to the “binder” program when creating a 32-bit static simulation or EMA executable.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_static_flags_64bit
Specifies optional flags to be passed to the “binder” program when creating a 64-bit static simulation or EMA executable.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_static_flags_devel
Specifies optional flags to be passed to the “binder” program when creating a static development simulation or EMA executable.
| Data Type | Default Value |
|---|---|
| string | Windows: “/DEBUG” Linux: “-g” |
bind_static_flags_optim
Specifies optional flags to be passed to the “binder” program when creating a static executable for an optimized simulation kernel.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_static_libs
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into an executable program). The binder program is indirectly invoked through the ECI program specified by the bind_static_prog preference. The value of bind_static_libs should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_static_libs_32bit
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into an executable program) for a 32-bit simulation kernel. The binder program is indirectly invoked through the ECI program specified by the bind_static_prog preference. The value of bind_static_libs_32bit should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_static_libs_64bit
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into an executable program) for a 64-bit simulation kernel. The binder program is indirectly invoked through the ECI program specified by the bind_static_prog preference. The value of bind_static_libs_64bit should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_static_libs_devel
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into an executable program) for a development simulation kernel. The binder program is indirectly invoked through the ECI program specified by the bind_static_prog preference. The value of bind_static_libs_devel should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_static_libs_optim
Specifies optional libraries to be passed to the “binder” program (the ECI translator that causes object code files to be linked into an executable program) for an optimized simulation kernel. The binder program is indirectly invoked through the ECI program specified by the bind_static_prog preference. The value of bind_static_libs_optim should be a list of one or more library names separated by spaces. Library names can be simple file names from the current working directory or (preferably) full path names.
| Data Type | Default Value |
|---|---|
| string | “” |
bind_static_prog
Specifies the ECI translation program or script to invoke to create static executables. Changing the default value of this preference may necessitate a change of the flags passed to the ECI program by the bind_static_flags preference.
| Data Type | Default Value |
|---|---|
| string | Windows: bind_msvc Linux: bind_unix |
| Built-in Scripts (Windows) | - bind_msvc – use Microsoft Visual Studio C/C++ linker |
| Built-in Scripts (Linux) | - bind_gcc – link executable with gcc - bind_g++ – link executable that contains C++ code with gcc - bind_cc_purify – same as bind_cc, plus instrument the resulting executable with IBM Rational Purify - bind_CC_purify – same as bind_CC, plus use Purify - bind_gcc_purify – same as bind_gcc, plus use Purify - bind_gcc_quantify – same as bind_gcc, plus instrument the resulting executable with IBM Rational Quantify - bind_CC_quantify – same as bind_CC, plus use Quantify - bind_unix – use default for architecture (equivalent to bind_g++ on Linux) |
check_newer_process_model_files
Specifies the dates to consult when recompiling a file. If FALSE, only object file dates are checked. If TRUE, both object and process model file dates are checked.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
code_auto_indenting
Specifies whether to automatically indent C/C++ code. If TRUE, code editors automatically insert an appropriate amount of indent for each new line.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
code_brace_matching
Specifies whether to do live brace matching on C/C++ code. If TRUE, code editors highlight the matching left brace when a right brace is typed.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
code_coloring
Specifies whether C/C++ code is color-coded in text edit pads. If both this preference and the Syntax Highlighting operation in the edit pad’s Options menu are enabled, text is color-coded.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
code_coloring.c_keyword_color
Specifies the color of C keywords when color coding (syntax highlighting) is enabled.
| Data Type | Default Value |
|---|---|
| string | #0000FF |
code_coloring.char_literal_color
Specifies the color of character literals when color coding (syntax highlighting) is enabled.
| Data Type | Default Value |
|---|---|
| string | #22C2C2 |
code_coloring.comment_color
Specifies the color of comments when color coding (syntax highlighting) is enabled.
| Data Type | Default Value |
|---|---|
| string | #B22222 |
code_coloring.directive_color
Specifies the color of preprocessor directives when color coding (syntax highlighting) is enabled.
| Data Type | Default Value |
|---|---|
| string | #B69500 |
code_coloring.number_color
Specifies the color of numbers when color coding (syntax highlighting) is enabled.
| Data Type | Default Value |
|---|---|
| string | #000000 |
code_coloring.op_keyword_color
Specifies the color of keywords (such as kernel procedures) when color coding (syntax highlighting) is enabled.
| Data Type | Default Value |
|---|---|
| string | #9919E5 |
code_coloring.state_variable_color
Specifies the color of global keywords when color coding (syntax highlighting) is enabled.
| Data Type | Default Value |
|---|---|
| string | #3F3F7F |
code_coloring.string_literal_color
Specifies the color of string literals when color coding (syntax highlighting) is enabled.
| Data Type | Default Value |
|---|---|
| string | #22B222 |
code_coloring.user_keyword_color
Specifies the color of user keywords when color coding (syntax highlighting) is enabled. List the keywords you want color-coded in the code_coloring.user_keywords preference.
| Data Type | Default Value |
|---|---|
| string | #FF5FFF |
code_coloring.user_keywords
List of words you specify that will be color-coded. The color applied to words in this list is specified by the code_coloring.user_keyword_color preference.
| Data Type | Default Value |
|---|---|
| string list | <empty> |
code_editor_prog
Specifies the path to a text editor program used to view and edit C/C++ code. The default program is whatever editor is used for editing general text, as specified by the editor_prog preference.
| Data Type | Default Value |
|---|---|
| string | “editor_prog” |
comp_flags_32bit
Specifies optional flags passed to a C/C++ compiler when compiling code for a 32-bit library or executable. These flags will be combined with the flags specified by other comp_flags_ preferences (comp_flags_common and others, as needed) and passed to the compiler program.
The value of this preference is compiler-specific and must have a format that is accepted by the compiler being used. For example, compiler flags are typically preceded by a dash.
Note: When you specify a dash-preceded value for this preference on a command line, either the dash must be represented by a carat (-bind_static_flags ^g) or the value must be enclosed in double quotes, with a space character preceding the dash (for example, -bind_static_flags “ -g”).
| Data Type | Default Value |
|---|---|
| string | Windows: “” Linux: “” |
comp_flags_64bit
Specifies optional flags passed to a C/C++ compiler when compiling code for a 64-bit library or executable. These flags will be combined with the flags specified by other comp_flags_ preferences (comp_flags_common and others, as needed) and passed to the compiler program.
The value of this preference is compiler-specific and must have a format that is accepted by the compiler being used. For example, compiler flags are typically preceded by a dash.
Note: When you specify a dash-preceded value for this preference on a command line, either the dash must be represented by a carat (-bind_static_flags ^g) or the value must be enclosed in double quotes, with a space character preceding the dash (for example, -bind_static_flags “ -g”).
| Data Type | Default Value |
|---|---|
| string | Windows: “/GS- /Wp64” Linux: “” |
comp_flags_c++_specific
Specifies optional flags passed to a C or C++ compiler when compiling C++ code. These flags will be combined with the flags specified by other comp_flags_ preferences (comp_flags_common and others, as needed) and passed to the compiler program.
The value of this preference is compiler-specific and must have a format that is accepted by the compiler being used. For example, compiler flags are typically preceded by a dash.
Note: When you specify a dash-preceded value for this preference on a command line, either the dash must be represented by a carat (-bind_static_flags ^g) or the value must be enclosed in double quotes, with a space character preceding the dash (for example, -bind_static_flags “ -g”).
| Data Type | Default Value |
|---|---|
| string | “” |
comp_flags_c_specific
Specifies optional flags passed to a C or C++ compiler when compiling C code. These flags will be combined with the flags specified by other comp_flags_ preferences (comp_flags_common and others, as needed) and passed to the compiler program.
The value of this preference is compiler-specific and must have a format that is accepted by the compiler being used. For example, compiler flags are typically preceded by a dash.
Note: When you specify a dash-preceded value for this preference on a command line, either the dash must be represented by a carat (-bind_static_flags ^g) or the value must be enclosed in double quotes, with a space character preceding the dash (for example, -bind_static_flags “ -g”).
| Data Type | Default Value |
|---|---|
| string | “” |
comp_flags_common
Specifies optional compiler flags (such as include paths) to be used for all compilations. These flags will be combined with the flags specified by other comp_flags_ preferences (as needed) and passed to the compiler program.
The value of this preference is compiler-specific and must have a format that is accepted by the compiler being used. For example, compiler flags are typically preceded by a dash.
Note: When you specify a dash-preceded value for this preference on a command line, either the dash must be represented by a carat (-bind_static_flags ^g) or the value must be enclosed in double quotes, with a space character preceding the dash (for example, -bind_static_flags “ -g”).
| Data Type | Default Value |
|---|---|
| string | Windows: “/D_CRT_SECURE_NO_DEPRECATE /W3 /I <install_dir><release>\models\std\include” ¹ Linux: “-I <install_dir>/<release>/models/std/include” ² |
Note 1: Will also include “/DOP_ODK_APIS” if ODK is selected in the product options.
Note 2: Will also include “-DOP_ODK_APIS” if ODK is selected in the product options.
comp_flags_devel
Specifies optional compiler flags to be used when compiling code in development mode. These flags will be combined with the flags specified by other comp_flags_ preferences (comp_flags_common and others, as needed) and passed to the compiler program. The default values represent the debugging flags for GNU, Microsoft, and Intel compilers.
The value of this preference is compiler-specific and must have a format that is accepted by the compiler being used. For example, compiler flags are typically preceded by a dash.
Note: When you specify a dash-preceded value for this preference on a command line, either the dash must be represented by a carat (-bind_static_flags ^g) or the value must be enclosed in double quotes, with a space character preceding the dash (for example, -bind_static_flags “ -g”).
| Data Type | Default Value |
|---|---|
| string | Windows: “/Zi /Od” Linux: “-g” |
comp_flags_mt
Specifies optional compiler flags to be used when compiling code in parallel mode. These flags will be combined with the flags specified by other comp_flags_ preferences (comp_flags_common and others, as needed) and passed to the compiler program.
The value of this preference is compiler-specific and must have a format that is accepted by the compiler being used. For example, compiler flags are typically preceded by a dash.
Note: When you specify a dash-preceded value for this preference on a command line, either the dash must be represented by a carat (-bind_static_flags ^g) or the value must be enclosed in double quotes, with a space character preceding the dash (for example, -bind_static_flags “ -g”).
| Data Type | Default Value |
|---|---|
| string | “” |
comp_flags_optim
Specifies optional compiler flags to be used when compiling code in optimized mode. These flags will be combined with the flags specified by other comp_flags_ preferences (comp_flags_common and others, as needed) and passed to the compiler program. The default value represents some optimization flags for Microsoft and GNU compilers.
The value of this preference is compiler-specific and must have a format that is accepted by the compiler being used. For example, compiler flags are typically preceded by a dash.
Note: When you specify a dash-preceded value for this preference on a command line, either the dash must be represented by a carat (-bind_static_flags ^g) or the value must be enclosed in double quotes, with a space character preceding the dash (for example, -bind_static_flags “ -g”).
| Data Type | Default Value |
|---|---|
| string | Windows compiler /Ox /Ob2 /DOPD_NO_DEBUG /DOPD_INLINE_KPS gcc compiler (on Linux) -02 -DOPD_NO_DEBUG -DOPD_INLINE_KPS |
comp_globals_export
When creating shared object libraries, specifies whether the library will require functions and variables declared in other libraries. If true, any variable declared with IMPORT_GLOBAL will look in other libraries for definition.
Required under Windows only.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
comp_per_file_errors
Specifies whether op_runsim and op_mksim should write compiler messages to a single file or separate files. A single file reduces clutter in the tmp directory. Separate files can make it easier to find the messages for a specific source file.
When FALSE, each compilation process produces one cc_err output file containing warning and error messages for the last source file compiled. When TRUE, compilation produces a separate cc_err file for each source file that generates messages. For separate cc_err files, each file name includes the suffix “-#”, where # is the compilation index of the corresponding source file (as shown in “Compiling … [# of ##]”).
File names might also include a process number, as specified by the comp_per_process_errors preference. For a discussion of compilation output files, see Controlling Compilation Output Files.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
comp_per_process_errors
Specifies whether cc_err output files from op_runsim and op_mksim should have a process ID appended to their names. Without the process ID suffix, all compilation output files have the same name and automatically overwrite older versions. This can be a problem if the output files are overwritten before you have a chance to look at them. This is especially a problem if you are using multiple op_mko invocations at the same time, such as with makefile.
When FALSE, a process ID is not included in the file name. When TRUE, the process ID of the compilation process (such as op_mko or op_runsim) is appended to the file name (cc_err_<pid>).
File names might also include an index number, as specified by the comp_per_file_errors preference. For a discussion of compilation output files, see Controlling Compilation Output Files.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
comp_prog
Specifies the name of the ECI translation program or script that should be invoked to compile C source code. Changing the value of this preference might necessitate a change of the flags passed to the C compiler program by the comp_flags_c_specific preference.
| Data Type | Default Value |
|---|---|
| string | Windows: comp_msvc Linux: comp_unix |
| Built-in Scripts (Windows) | - comp_icl – use Intel C/C++ compiler - comp_msvc – use Microsoft Visual Studio C compiler |
| Built-in Scripts (Linux) | - comp_gcc – use gcc C compiler - comp_gcc_lint – pre-process files with lint (for extra code checks) and compile with gcc C compiler- comp_gcc_paranoid – compile with gcc C compiler with lots of code validation checks - comp_icc – use Intel C compiler (available only for Linux) - comp_unix – use C compiler default for architecture (equivalent to comp_gcc on Linux) |
comp_prog_cpp
Specifies the name of the ECI translation program or script that should be invoked to compile C++ source code. Changing the value of this preference might necessitate a change of the flags passed to the C++ compiler program by the comp_flags_c++_specific preference.
| Data Type | Default Value |
|---|---|
| string | Windows: comp_msvc Linux: comp_unix_cpp |
| Built-in Scripts (Windows) | - comp_icl – use Intel C/C++ compiler - comp_msvc – use Microsoft Visual Studio C++ compiler |
| Built-in Scripts (Linux) | - comp_g++ – use gcc C++ compiler - comp_unix_cpp – use C++ compiler default for architecture (equivalent to comp_g++_3 on Linux) |
comp_trace_info
Specifies whether compiled code should include additional trace information. When TRUE, additional trace information is included. When FALSE, source code is compiled as-is. The default (kernel_based) acts like TRUE for development kernels and FALSE for optimized kernels.
| Data Type | Constraints | Default Value |
|---|---|---|
| enum | kernel_based, TRUE, FALSE | “kernel_based” |
core_dump
Forces a program to retain its state in a core file in the current directory if the program encounters a program fault (segmentation violations, floating exceptions, or bus errors). These are typically caused by an improperly trapped condition (for instance, dividing by zero). When such errors occur, use the op_vuerr utility to see where the error occurred.
If you contact technical support, you might be asked to run the program debugger dbx. The core dump created by this preference allows the error to be partially analyzed without having to recreate it while the program is running under dbx. Setting this preference does not affect the normal operation of programs.
This preference is usable only on Linux platforms.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
debug_mk
Specifies that a program print to standard output the exact compiling and linking commands (including flags) it sends to the operating system. This can be useful when you have trouble compiling or linking process-model or other code.
Note: Printing the actual command will typically cause the top-level compiling or linking operation to fail. Therefore, you should have this preference set to TRUE only while performing diagnostics or debugging.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
des.checkpoint.enabled
Specifies whether the checkpoint/restart feature should be enabled. When TRUE, checkpointing is enabled; the checkpoint library will be loaded and memory paging turned off. For details on this feature, see "Checkpoints" on page 419.
This preference can be used only from the command line and only on Linux.
| Type | Default Value |
|---|---|
| boolean | FALSE |
des.windows_32bit_debugger_executable_path
Specifies the path to the command-line Windows debugger executable (cdb.exe) for debugging 32-bit processes.
| Type | Default Value |
|---|---|
| string | “C:\Program Files\Debugging Tools for Windows\cdb.exe” |
des.windows_64bit_debugger_executable_path
Specifies the path to the command-line Windows debugger executable (cdb.exe) for debugging 64-bit processes.
| Type | Default Value |
|---|---|
| string | “C:\Program Files\Debugging Tools for Windows 64-bit\cdb.exe” |
ema_verbose
Specifies that EMA application code generated by an opnet tool include assignments for all object attributes, even those attributes with default values. Non-verbose EMA application code only includes assignment for attributes that have non-default values.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
ets_obj.attr_set_recoverable_errors
Specifies whether to generate a recoverable error when an attempt to set an attribute via an ETS call fails. If TRUE, recoverable errors are generated whenever certain ETS functions return failure. This preference should generally be set to FALSE unless you are developing ETS code.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
ets_obj.attr_set_strict
Specifies whether to test the validity of symbols and attribute values strictly when setting attribute values via an ETS call. When FALSE, value limits are ignored and symbols are not verified when setting attributes. However, even if the values are not validated, a later model-wide validation operation (such as reopening the model) might force the attribute to a valid value.
Note: This is a performance preference and should be used only when the ETS code is guaranteed to use only valid attribute values.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
kernel_type
Specifies whether an optimized or development DES kernel should be used.
| Data Type | Constraints | Default Value |
|---|---|---|
| enum | development, optimized | development |
m32
When TRUE, specifies that a 32-bit DES kernel should be used. This preference is mutually exclusive with m64; only one of these preferences should be used.
This preference can be used only from the command line.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
m64
When TRUE, specifies that a 64-bit DES kernel should be used. This preference is mutually exclusive with m32; only one of these preferences should be used.
This preference can be used only from the command line.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
mem_opt.compact_pools
Specifies whether to re-use memory pools of identical size. When TRUE, memory pools are re-used.
The value of this preference changes only at startup.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
mem_opt.grow_pool_planks
When TRUE, specifies that the size of memory pool planks should be dynamically increased when deemed appropriate.
The value of this preference changes only at startup.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
mem_opt.pool_small_blocks
When TRUE, specifies that memory pools should be used for small blocks of memory.
The value of this preference changes only at startup.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
mem_shred
Specifies whether to set the contents of memory being freed to 0xDF. When TRUE, memory is shredded.
This preference can be used on the command line only, and its value changes only at startup.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
mem_track
Specifies that the memory allocation and deallocation tracking features of the program should be enabled for use within the host workstation debugger. If mem_track is enabled, internal program functions can be invoked to print lists of the allocation sources and deallocation sinks within the program. This is accomplished by invoking the function Vos_Memstats_Print_Sources (obj_name, mode) where the string argument obj_name is the name of a particular memory object and mode is either 0 (for a list of allocation sources) or 1 (for a list of deallocation sinks). To obtain a list of significant memory object names, invoke the function Vos_Memstats_Print_Table (1, 2). If mem_track is disabled, these functions are not functional.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
mem_track_object
Specifies the name of a particular object to track memory allocation and deallocation. Specifying an object allows for efficient tracking if only one object is of interest. This preference is used only when mem_track is TRUE.
| Data Type | Default Value |
|---|---|
| string | “” |
mt
Specifies that a parallel DES kernel should be used. This preference can be used only from the command line.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
no_fin_required_for_state_vars
Specifies whether process models require a FIN macro for access to state variables. When TRUE, no FIN is required, but the resulting process model code runs a bit slower.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
ov_diff_tolerance
Specifies a tolerance, expressed as a percentage value, to use when testing the equality of graphs. Vectors whose mean values differ by less than this tolerance will be considered equal.
| Data Type | Default Value |
|---|---|
| integer | 5 |
ov_mem_size
Specifies the maximum size of the output vector data buffer in megabytes. When a buffer reaches the specified limit, its entries are written to disk, and it resumes the collection of new values. Setting this preference to larger values than the default trades off less writes to disk versus more memory usage. If fragments are allowed to grow too large, the simulation may need to use swap space which will reduce execution speed.
| Type | Default Value |
|---|---|
| integer | 4 |
prof_output
Specifies a file name or other destination to which function profiling information should be sent.
| Data Type | Default Value |
|---|---|
| string | “console” |
prof_output_separator
Specifies text to be placed between function profile fields.
| Data Type | Default Value |
|---|---|
| string | “” |
prof_track
Specifies that function profiling information be reported where possible. When a simulation is run, the program reports the number of times each function was called, and how many seconds were spent within that function.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
prof_track_func
Specifies a single function for which to report tracking information (if prof_track is enabled).
| Data Type | Default Value |
|---|---|
| string | “” |
prof_track_recurse
Collects profiling information on recursive function calls (if prof_track is enabled).
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
progress_bar_location
Specifies the initial screen location of progress bars.
| Data Type | Constraints | Default Value |
|---|---|---|
| enum | center, lower_right, lower_left, upper_right, upper_left | “center” |
progress_bar_logging
Specifies which, if any, progress bar calls are recorded in the session log.
| Data Type | Constraints | Default Value |
|---|---|---|
| enum | none, record_starts_ends, record_advances | “none” |
progress_bar_positioning
Specifies the positioning of progress bars. If “recenter”, progress bars are kept centered on the current window. If “fixed”, they remain in a fixed global position.
| Data Type | Constraints | Default Value |
|---|---|---|
| enum | recenter, fixed | “recenter” |
show_compilation_output
Specifies whether to display the output of each compilation, even if successful. When TRUE, compilation output is always displayed.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
show_compilation_success_dialog
Specifies whether to display a dialog box listing the expected targets and the compilation status of each.
| Data Type | Default Value |
|---|---|
| boolean | TRUE |
verbose_mk
Specifies that all commands issued to compile and bind code be displayed.
| Data Type | Default Value |
|---|---|
| boolean | FALSE |
Controlling Compilation Output Files
Compilations can be started in various ways: from the GUI, from command-line invocations of op_mko or op_mkso, and when building simulations (op_runsim and op_mksim). A compilation process (such as a specific instance of op_mko or op_runsim) can compile many source files. For example, you might use the Process Editor’s Compile operation many times during a Modeler session, or op_runsim might need to recompile all model files before running a simulation. By default, Modeler creates one compilation output file for each process. The output file contains compiler output messages (warnings, errors, and so on) only for the last source file compiled by the process.
There are two preferences you can use to control how compiler output files are generated and named: comp_per_file_errors and comp_per_process_errors. These preferences interact as follows:
Table 18: Interaction of Preferences for Producing Compiler Output
| Value of comp_per_process_errors | Value of comp_per_file_errors | Result |
|---|---|---|
| FALSE | FALSE | One output file that contains all messages from a compilation process’ last compilation. The output file will be overwritten by newer compilations. Example file name: cc_err |
| FALSE | TRUE | Multiple output files for a compilation process (one file for each source file that generates messages). An output file will not be overwritten by newer compilations until the corresponding index is reused. Example file names: cc_err-1, cc_err-2, cc_err-4 |
| TRUE | FALSE | [default] One output file per compilation process (each file contains compilation messages from the process’ last compilation). An output file will not be overwritten by newer compilations until the corresponding process ID is reused. Example file name: cc_err_2765 |
| TRUE | TRUE | Multiple output files for each compilation process (for each process, one file for each source file that generates messages). Produces largest number of files, but allows quick access to messages for a specific source file. An output file will not be overwritten by newer compilations until the corresponding process ID and index are reused. Example file names: cc_err_2765-3, cc_err_2765-4 |