Show: Object Pascal C++
Display Preferences

Paths and Directories (C++)

From Appmethod Topics
Jump to: navigation, search

Go Up to C++ Options

Tools > Options > Environment Options > C++ Options > Paths and Directories

Use the Paths and Directories page to specify directories, compiler, and linker options for all packages.

Item Description

Selected Platform

Specifies the target platform to which the settings on this page are to apply. For example, if you select OS X, the paths and directories apply to the Mac OS X platform.

The fields are preloaded with the specific paths and directories for each supported target platform. You can choose among the platforms that are enabled for the current project.

System Include path

Specifies the directories with header files used by default for C++ projects.

Library path

Specifies where to find C++ header and library files for installed components and packages. This is the C++ global library path.

User include path (for BCC64)

The paths from user includes are searched before the ones from System includes. So you can specify user include paths in order to override a system header (that is, provide your own version).

Package output directory

Specifies where the compiler should put compiled packages files.

BPI / LIB output directory

Specifies where package bpi and lib files are placed by default. The lib is a static library and the bpi is an import library. The default specified here can be overridden in individual packages by using the package options.

Browsing path

Specifies directories where the Code Browsing feature of the Code Editor searches for files when it cannot find an identifier on the project search path or source path.

Restrict refactoring path

Specifies the directories that you want to restrict from refactoring. For example, if you attempt to rename a symbol, and a reference is found in a file on one of the paths specified here, the refactoring ends with an error message.

The following built-in directories are automatically restricted from refactoring:

  • $(BDS)\include\fmx
  • $(BDS)\include\dinkumware

These paths restrict refactoring from our component library sources and the Dinkumware STL sources.

If you are using other third-party libraries (such as Boost), enter in this field the path where the library header files are located.

Tip: You can enter a path relative to the Appmethod root directory using the $(BDS) environment variable.
Personal tools
In other languages