Previous: Configuring with GPRconfig, Up: Gprbuild [Contents][Index]
A text file using the project file syntax. It defines languages and their characteristics as well as toolchains for those languages and their characteristics.
GPRbuild needs to have a configuration file to know the different characteristics of the toolchains that can be used to compile sources and build libraries and executables.
A configuration file is a special kind of project file: it uses the same syntax as a standard project file. Attributes in the configuration file define the configuration. Some of these attributes have a special meaning in the configuration.
The default name of the configuration file, when not specified to GPRbuild by switches --config= or --autoconf= is default.cgpr. Although the name of the configuration file can be any valid file name, it is recommended that its suffix be .cgpr (for Configuration GNAT Project), so that it cannot be confused with a standard project file which has the suffix .gpr.
When default.cgpr cannot be found in the configuration project path, GPRbuild invokes GPRconfig to create a configuration file.
In the following description of the attributes, when an attribute is an
associative array indexed by the language name, for example
Spec_Suffix (<language>)
, then the name of the language is case insensitive.
For example, both C
and c
are allowed.
Any attribute may appear in a configuration project file. All attributes in a configuration project file are inherited by each user project file in the project tree. However, usually only the attributes listed below make sense in the configuration project file.