4.3 Compiler Flags

Compiler flags are highly specific to individual compilers and subject to change at any time entirely beyond the control of Rogue Wave. Therefore, we will not attempt to document them here because of the difficulty of keeping such documentation up-to-date and accurate.

There are, however, a few general principles you can follow:

If you are building a DEBUG version of Rogue Wave libraries or applications that depend on such libraries, you will probably want to set the compiler's flag for symbolic debugging.
Similarly, when compiling multithreaded libraries or applications, you need to set a flag to enable multithreading.
When compiling with MSVC, you will need to specify a flag to link to the correct system library, as shown in the following table:

Table 13 -- Flags for specifying MSVC system libraries

Build type #s	Build type name	Compiler flag	Flag description
0s, 8s	singlereleaselib	`-ML`	Link with `LIBC.LIB`.
3s, 11s	singledebuglib	`-MLd`	Link with `LIBCD.LIB`.
4s, 12s	multireleaselib	`-MT`	Link with `LIBCMT.LIB`.
7s, 15s	multidebuglib	`-MTd`	Link with `LIBCMTD.LIB`.
4d, 12d	multireleasedll	`-MD`	Link with `LIBCRT.LIB`.
7d, 15d	multidebugdll	`-MDd`	Link with `LIBCRTD.LIB`.

The Borland compiler uses the following flags to indicate whether to build a GUI or a console application:

Table 14 -- Borland flags for GUI versus console applications

Flag	Description	Build type #s
`-W`	Build a GUI EXE.	0s, 3s, 4s, 7s, 8s, 11s, 12s, 15s
`-WC`	Build a console EXE.	0s, 3s, 4s, 7s, 8s, 11s, 12s, 15s
`-WDE`	Build a GUI DLL.	4d, 7d, 12d, 15d
`-WDCE`	Build a console DLL.	4d, 7d, 12d, 15d

For more detailed information on the compiler flags needed for particular build types, consult your compiler documentation or the product-specific build guides for Rogue Wave products.