paweld/fpc
1
0
Fork 0
mirror of https://gitlab.com/freepascal.org/fpc/source.git synced 2025-12-04 17:47:39 +01:00
Code Issues Packages Projects Releases Wiki Activity

* Renamed ppc.cfg -> fpc.cfg

Browse Source
This commit is contained in:
carl 2001-11-23 12:15:08 +00:00
parent d5be05efa7
commit 7f9978806a
1 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/user.tex
View File

@ -331,14 +331,14 @@ as it will attempt to create the directories you specify.
In principle, you can install it wherever you want, though.
At the end of installation, the installation program will generate a
configuration file (\file{ppc.cfg}) for the \fpc compiler which
configuration file (\file{fpc.cfg}) for the \fpc compiler which
reflects the settings that you chose. It will install this file in
the \file{/etc} directory or in your home directory (with name
\file{.ppc.cfg}) if you do not have write permission in the \file{/etc}
\file{.fpc.cfg}) if you do not have write permission in the \file{/etc}
directory. It will make a copy in the directory where you installed the
libraries.
The compiler will first look for a file \file{.ppc.cfg} in your home
The compiler will first look for a file \file{.fpc.cfg} in your home
directory before looking in the \file{/etc} directory.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@ -352,7 +352,7 @@ following variables :
\begin{itemize}
\item \verb|PPC_EXEC_PATH| contains the directory where support files for
the compiler can be found.
\item \verb|PPC_CONFIG_PATH| specifies an alternate path to find the \file{ppc.cfg}.
\item \verb|PPC_CONFIG_PATH| specifies an alternate path to find the \file{fpc.cfg}.
\item \verb|PPC_ERROR_FILE| specifies the path and name of the error-definition file.
\item \verb|FPCDIR| specifies the root directory of the \fpc installation.
(e.g : \verb|C:\PP\BIN|)
@ -431,7 +431,7 @@ Here we describe the essentials to compile a program and a unit.
For more advanced uses of the compiler, see the section on configuring
the compiler, and the \progref{}.
The examples in this section suppose that you have a \file{ppc.cfg} which
The examples in this section suppose that you have a \file{fpc.cfg} which
is set up correctly, and which contains at least the path setting for the
RTL units. In principle this file is generated by the installation program.
You may have to check that it is in the correct place (see section
@ -553,7 +553,7 @@ If the compiler doesn't find a compiled version of the unit, or when the
manner for the unit source file, and attempt to recompile it.
It is recommended to set the unit search path in the configuration file
\file{ppc.cfg}. If you do this, you don't need to specify the unit search
\file{fpc.cfg}. If you do this, you don't need to specify the unit search
path on the command-line every time you want to compile something.
% Include files.
@ -608,19 +608,19 @@ You can add files to the object file search path with the \seeo{Fo} option.
Starting from version 1.0.6 of the compiler, usage of the
file \file{ppc386.cfg} is considered deprecated. The file
should now be called \file{ppc.cfg} and will work for
all processor targets. For compatibility, \file{ppc.cfg} will
should now be called \file{fpc.cfg} and will work for
all processor targets. For compatibility, \file{fpc.cfg} will
be searched first, and if not found, the file \file{ppc386.cfg}
will be used.
Unless you specify the \seeo{n} option, the compiler will look
for a configuration file \file{ppc.cfg} in the following places:
for a configuration file \file{fpc.cfg} in the following places:
\begin{itemize}
\item Under \unix (such as \linux)
\begin{enumerate}
\item The current directory.
\item In your home directory, it looks for \file{.ppc.cfg}.
\item In your home directory, it looks for \file{.fpc.cfg}.
\item The directory specified in the environment variable
\var{PPC\_CONFIG\_PATH}, and if it's not set under \file{/etc}.
\end{enumerate}
@ -897,7 +897,7 @@ The output of the compiler can be controlled in many ways. This can be done
essentially in two distinct ways:
\begin{itemize}
\item Using command-line options.
\item Using the configuration file: \file{ppc.cfg}.
\item Using the configuration file: \file{fpc.cfg}.
\end{itemize}
The compiler first reads the configuration file. Only then the command line
options are checked. This creates the possibility to set some basic options
@ -1215,7 +1215,7 @@ compiler to define only some very basic types.
% Using the configuration file
\section{Using the configuration file}
\label{se:configfile}
Using the configuration file \file{ppc.cfg} is an alternative to command
Using the configuration file \file{fpc.cfg} is an alternative to command
line options. When a configuration file is found, it is read, and the lines
in it are treated like you typed them on the command line. They are treated
before the options that you type on the command line.
@ -1381,15 +1381,15 @@ have the global options that are set in a global configuration file.
Example:
\begin{verbatim}
#IFDEF LINUX
#INCLUDE /etc/ppc.cfg
#INCLUDE /etc/fpc.cfg
#ELSE
#IFDEF GO32V2
#INCLUDE c:\pp\bin\ppc.cfg
#INCLUDE c:\pp\bin\fpc.cfg
#ENDIF
#ENDIF
\end{verbatim}
This will include \file{/etc/ppc.cfg} if you're on a linux machine,
and will include \verb+c:\pp\bin\ppc.cfg+
This will include \file{/etc/fpc.cfg} if you're on a linux machine,
and will include \verb+c:\pp\bin\fpc.cfg+
on a dos machine.
\subsection{\#SECTION}