Configuration file

From Lazarus wiki
Revision as of 13:52, 14 July 2016 by FPC user (talk | contribs) (example and sections)
Jump to navigationJump to search


To avoid having to include compiler options in build files or repeat them on the command line, Free Pascal allows them to be placed in a configuration file. The compiler options in the file will be read along with options given on the command line, with the configuration file being processed first.


One command line option is written per line with the same format as when used on the command line.


Comment lines are allowed. They follow the Unix shell/Python/Perl comment-style: a '#' signifies the start of a comment.


# Perform range checking, IO checking, overflow checking, IEEE error checking


The file is named fpc.cfg, unless it is located in the HOME directory on a Unix-like system, in which case it will follow Unix configuration file convention and start with a '.' ( .fpc.cfg ).


  • Under a Unix or Unix-like operating systems (e.g. Linux, FreeBSD)
  1. The current directory.
  2. Your home directory, it looks for .fpc.cfg.
  3. The directory specified in the environment variable PPC_CONFIG_PATH, and if it is not set, it will look in the etc directory above the compiler directory. (For instance, if the compiler is in /usr/local/bin, it will look in /usr/local/etc)
  4. The directory /etc.
  • Under all other operating systems:
  1. The current directory.
  2. If it is set, the directory specified in the environment variable PPC_CONFIG_PATH.
  3. The directory where the compiler is.

Not Combined

Unlike Unix shell configuration files, FPC configuration files are not combined. It will only use the first one that it finds and ignore any others that may also be on the system, including the configuration file that comes with Free Pascal.


You can tell the compiler to not use a configuration file by giving the -n command line option.