3.1.5 Configuration file

Not all options must be given on the compiler command line. The compiler can use a configuration file which can contain the same options as on the command line. There can be only one command-line option on each line in the configuration file.

Unless you specify the -n (see page 104) option, the compiler will look for a configuration file fpc.cfg in the following places:

• Under unix (such as linux)

  1.

  The current directory.

  2.

  Your home directory, it looks for .fpc.cfg.

  3.

  The directory specified in the environment variable PPC_CONFIG_PATH.

  4.

  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.
  See below for some additional information about this point.

  5.

  The directory /etc.

• Under all other OSes:

  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.

Remark Note that the compiler directory is determined by the location of the actual compiler binary. This has 2 consequences:

1.

The default installation on unix places this under /usr/local/lib/fpc, or /usr/lib/fpc. It places several symlinks in /usr/local/bin or /usr/bin. These symlinks are not considered when looking for the configuration file(s), so the places to look for the configuration file are /usr/local/lib/fpc/etc, or /usr/lib/fpc/etc.

2.

The fpc command is not the actual compiler binary. The fpc command selects the actual compiler binary based on e.g. the CPU target. The actual compiler binary is called ppcXYZ.

3.

The actual installation directory may vary: /usr/local/bin may be /usr/bin, depending on the packager.