MAN page from openSUSE Leap 42 fpc-2.6.4-1.1.i586.rpm
Section: Free Pascal Makefile.fpc format (5)
Updated: 12 Dec 1999Index
Makefile.fpc - Configuration file for fpcmake.
is a configuration file for the fpcmake command. Starting from this file aMakefile
is created to compile Free Pascal units and programs.
Makefile.fpcis a plain ASCII file that contains a number of sections as in a Windowsinifile. The following sections are recognized (in alphabetical order):
- Specifies rules for cleaning the directory of units and programs. The following entries are recognized:
- names of all units that should be removed when cleaning. Don't specifyextensions, the makefile will append these by itself.
- names of files that should be removed. Specify full filenames.
- The defaults section contains some default settings. The following keywordsare recognized:
- Contains instructions for installation of your units and programs. Thefollowing keywods are recognized:
Units will be installed in the subdirectory units/$(OS_TARGET)of the dirbaseentry.
- the directory below wchich all installs are done. This corresponds to the--prefixargument to GNU configureIt is used for the installation of programs and units. By default, this is /usron linux, and /ppon all other platforms.
- The directory that is used as the base directory for the installation ofunits. Default this is dirprefix appended with/lib/fpc/FPC_VERSIONfor linux or simply the dirprefix on other platforms.
- This section specifies what units should be merged into a library, and whatexternal libraries are needed. It can contain the following keywords:
- the name of the library that should be created.
- a comma-separated list of units that should be moved into one library.
- a boolean value that specifies whether the gcc library is needed. This willmake sure that the path to the GCC library is inserted in the library searchpath.
- a boolean value that tells the makefile that other library directories will be needed.
- Which packages must be used. This section can contain the following keywords:
- A comma-separated list of packages that are needed to compile the targets.Valid for all platforms. In order to differentiate between platforms, youcan prepend the keywordpackageswith the OS you are compiling for, e.g. linuxpackagesif you want the makefile to use the listed packages on linux only.
- This is a boolean value (0 or 1) that indicates whether the FCL is used.
- This is a boolean value (0 or 1) that indicates whether the RTL should berecompiled.
- Anything that is in this section will be inserted as-is in the makefileafterthe makefile rules that are generated by fpcmake, but beforethe general configuration rules.In it, you cannot use variables that are defined by fpcmake rules, but youcan define additional rules and configuration variables.
- Anything that is in this section will be inserted as-is in the makefilebeforethe makefile target rules that are generated by fpcmake. This means that you cannot use any variables that are normally defined by
- In this section you can insert dependency rules and any other targets you wish to have. Do not insert 'default rules' here.
- Here you can specify which 'rule sections' should be included in the Makefile. The sections consist of a series of boolean keywords; each keyword decieswhether a particular section will be written to the makefile. By default,all sections are written.
You can have the following boolean keywords in this section.
- If this is set to true, then no sections are written.
- If set to false, fpcmake omits the rules for compiling units.
- If set to false, fpcmake omits the rules for compiling executables.
- If set to false, fpcmake omits the rules for assembling assembler files.
- If set to false, fpcmake omits the rules for compiling examples.
- If set to false, fpcmake omits the rules for making packages.
- If set to false, fpcmake omits the generic rules for compiling pascal files.
- If set to false, fpcmake omits the dependency rules.
- If set to false, fpcmake omits the rules for installing everything.
- If set to false, fpcmake omits the rules for installing the sources.
- If set to false, fpcmake omits the rules for installing archives.
- If set to false, fpcmake omits the rules for cleaning the directories.
- If set to false, fpcmake omits the rules for making libraries.
- If set to false, fpcmake omits the rules for composing the command-line based on the variousvariables.
- If set to false, fpcmake omits the rules for making libraries.
- If set to false, fpcmake omits the rules for running make in subdirectories..
- If set to false, fpcmake omits the rules for running some tools as the erchiver, UPX and zip.
- If set to false, fpcmake omits the rules for generating information.
- In this section you can define the various targets. The following keywordscan be used there:
- A space separated list of directories where make should also be run.
- A space separated list of example programs that need to be compiled whenthe user asks to compile the examples. Do not specify an extension, the extension will be appended.
- A space separated list of names of assembler files that must be assembled.Don't specify the extension, the extension will be appended.
- A space separated list of program names that need to be compiled. Do notspecify an extension, the extension will be appended.
- a list of rstfiles that needs to be converted to .po files for use with GNU gettextand internationalization routines.
- A space separated list of unit names that need to be compiled. Do notspecify an extension, just the name of the unit as it would appear un a usesclause is sufficient.
- In this section you can specify which tools are needed. Definitions touse each of the listed tools will be inserted in the makefile, dependingon the setting in this section.
Each keyword is a boolean keyword; you can switch the use of a tool on oroff with it.
The following keywords are recognised:
- Use ppdep the dependency tool. Trueby default.
- Useppumovethe Free Pascal unit mover.Trueby default.
- Use the ppufiletool to determine dependencies of unit files.Trueby default.
- Use sedthe stream line editor.Falseby default.
- use the data2inc tool to create include files from data files.Falseby default.
- Use the GNU difftool.Falseby default.
- Use the cmpfile comparer toolFalseby default.
- Use theupxexecutable packerTrueby default.
- use the datedate displaying tool.Trueby default.
- Use thezipfile archiver. This is used by the zip targets.Trueby default.
- This section can be used to make zip files from the compiled units andprograms. By default all compiled units are zipped. The zip behaviour canbe influencd with the presettings and postsettings sections.
The following keywords can be used in this unit:
- this file is the name of the zip file that will be produced.
- is the name of a makefile target that will be executed before the zip ismade. By default this is the installtarget.
- SEE ALSO
This document was created byman2html,using the manual pages.