[next] [prev] [prev-tail] [tail] [up]

#### 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 94) option, the compiler will look for a configuration file fpc.cfg in the following places:

- Under u n i x (such as l i n u x)
  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 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.

Versions prior to version 1.0.6 of the compiler used a configuration file ppc386.cfg. This file is still searched, but its usage is considered deprecated. For compatibility, fpc.cfg will be searched first, and if not found, the file ppc386.cfg will be searched and used.

Remark: The searching for ppc386.cfg will be removed from the compiler in version 2.4.0. To indicate this, the compiler gives a warning as of version 2.3.1 if it uses a ppc386.cfg configuration file.

[next] [prev] [prev-tail] [front] [up]