Directories and Conditionals

Go Up to Compiler Project Options Index

Project > Options > Directories and Conditionals

Use this page to set paths to your directories and conditional defines. The settings on this page affect all the tools on the Project > Options dialog, such as compilers and linkers.

Options	Description
Build Configuration Options	Described in Build Configuration Options.
Common Options	Described in Common Items on Project Options Pages.

Item	Description
BPI/Lib output: (-l)	Tells the linker to place bpi/lib output files in the directory specified, if they are generated. See the description of the pop-up button in Common Items on Project Options Pages.
Conditional Defines	Enter symbols that are referenced in conditional compiler directives. Use semicolons to separate multiple symbols. See the description of the pop-up button in Common Items on Project Options Pages.
Final output directory	Designates the directory where the final output of the build (such as the executable, OCX or DLL) is to be put. If you do not specify a final output directory, the intermediate output directory is used (described in this table). See the description of the pop-up button in Common Items on Project Options Pages.
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>). See the description of the pop-up button in Common Items on Project Options Pages.
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. See the description of the pop-up button in Common Items on Project Options Pages.
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 Library Path option 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. See the description of the pop-up button in Common Items on Project Options Pages.
Show general messages	Displays all output from the compiler and associated tools. After you select this option, click the down-arrow to select an available option (True, False).
_TCHAR maps to	Controls the floating definition of _TCHAR. The choices are wchar_t and char. See the description of the pop-up button in Common Items on Project Options Pages. Before you can set this option to wchar_t, your project must have an entry point called _tmain or _tWinMain. New projects (created with RAD Studio) have these entry points by default, but imported projects might need to have these entry points added by hand.Selecting wchar_t does the following: Sets the UNICODE and _UNICODE defines. Instructs the linker to use a library of wide versions. Instructs standard library and Windows API functions to float to their wide definitions. If you choose char, _TCHAR does not float to a wide definition. See Floating Functions.
Default	Saves the current settings as the default for each new project.

See Also

• _TCHAR Mapping
• Floating Functions
• Unicode in RAD Studio
• Enabling Applications for Unicode