Build Configuration options 

Description 

Build Configuration 

Displays the active build configuration. Use the drop-down menu to select another build configuration.  

Save As... 

Displays the Save As dialog box to save the current configuration's options to a file that can be loaded as a named option set.  

Load... 

Displays the Apply Option Set dialog box to apply the options in a named option set to the current configuration.  

Paths options 

Description 

Include path: (-I) 

Specifies the directories to be searched for include files. This is a set of include paths that are appended to any tool-specific include paths for the project as a whole. Standard include files are those you specify in angle brackets (<>) in an #include statement (for example, #include <myfile>). Click [...] to display a dialog allowing you to edit a list of paths. Check the Merge box to act as if the immediate ancestor's paths are merged into this list, though this list is not actually changed.  

Library Path: (-L) 

Specifies the directories the linker searches if there is no explicit path given for an .LIB module in the compile/link statement.
The Specify Library Search Path uses the following command-line syntax:
/L<PathSpec>[;<PathSpec>][..]
The linker uses the specified library search path(s) if there is no explicit path given for the .LIB file and the linker cannot find the library file in the current directory. For example, the command
ILINK32 /Lc:\mylibs;.\libs splash.\common\logo,,,utils logolib
directs the linker to first search the current directory for SPLASH.LIB. If it is not found in he current directory, the linker then searches for the file in the C:\MYLIBS directory, and then in the .\LIBs directory. However, notice that the linker does not use the library search paths to find the file LOGO.LIB because an explicit path was given for this file.
Click [...] to display a dialog to manage a list of paths. Check the Merge box to act as if the immediate ancestor's paths are merged into this list, though this list is not actually changed.  

Intermediate Output: 

Tells the linker to place intermediate output files in the directory specified. Also tells the compilers (dcc, bcc, tasm, brcc) where to put their compiled output; these are normally .obj and ..rcs files. Currently files that qualify for this placement are the linker state files. The .map file and .tds files go to the same directory as the output image, unless otherwise specified for the .map file.
Click [...] to display a directory selection dialog.  

Final Output: 

Designates the directory where the final output of the build, such as the executable or DLL, is put. Click [...] to display a directory selection dialog.  

BPI/Lib output: (-l) 

Tells the linker to place bpi/lib output files in the directory specified, if they are generated. Click [...] to display a directory selection dialog.  

Conditional Defines options 

Description 

Conditional Defines 

Defines the specified identifier name to the null string. -Dname=string defines name to string. In this assignment, string cannot contain spaces or tabs. You can also define multiple #define options on the command line using either of the following methods: This option applies to the entire project: all these defines are appended to those for specific compilers.
Include multiple definitions after a single -D option by separating each define with a semicolon (;) and assigning values with an equal sign (=). For example: BCC32.EXE -Dxxx;yyy=1;zzz=NO MYFILE.C
Include multiple -D options, separating each with a space. For example: BCC32.EXE -Dxxx -Dyyy=1 -Dzzz=NO MYFILE.C
Click [...] to display a dialog to manage a list of defines.Check the Merge box to act as if the immediate ancestor's defines are merged into this list, though this list is not actually changed.  

General option 

Description 

Default 

Saves the current settings as the default for each new project.