* Renamed ppc.cfg -> fpc.cfg

compiler/options.pas

@@ -1386,7 +1386,7 @@ begin
   else
    begin
      ppcaltcfg:='ppc386.cfg';
-     ppccfg:='ppc.cfg';
+     ppccfg:='fpc.cfg';
    end;
 
 { Order to read configuration file :
@@ -1394,7 +1394,7 @@ begin
    1 - current dir
    2 - configpath
    3 - compiler path
-  else try reading ppc.cfg in :
+  else try reading fpc.cfg in :
    1 - current dir
    2 - configpath
    3 - compiler path
@@ -1645,7 +1645,10 @@ finalization
 end.
 {
   $Log$
-  Revision 1.62  2001-11-23 02:48:46  carl
+  Revision 1.63  2001-11-24 02:09:54  carl
+  * Renamed ppc.cfg -> fpc.cfg
+
+  Revision 1.62  2001/11/23 02:48:46  carl
   + ppc.cfg is now configuration file for compiler.
     (first tries loading ppc386.cfg for backward compatibility)
 

docs/prog.tex

@@ -3207,7 +3207,7 @@ or dynamic libraries, there are 2 switches:
 Definition of one symbol will automatically undefine the other.
 
 These two switches can be used in conjunction with the configuration file
-\file{ppc386.cfg} or \file{ppc.cfg}. The existence of one of these symbols can be used to
+\file{fpc.cfg}. The existence of one of these symbols can be used to
 decide which unit search path to set. For example, on \linux:
 \begin{verbatim}
 # Set unit paths

ide/README

@@ -1,6 +1,6 @@
 
 You can have a fp.cfg file in the same directory as fp.exe. It works the
-same as ppc.cfg
+same as fpc.cfg
 
 To compile the IDE you need to choose whether to build with or without
 debugger (gdb) support. When debugger support is used a check will be

ide/fpswitch.pas

@@ -162,7 +162,7 @@ var
     BrowserSwitches,
     DirectorySwitches : PSwitches;
 
-{ write/read the Switches to ppc.cfg file }
+{ write/read the Switches to fpc.cfg file }
 procedure WriteSwitches(const fn:string);
 procedure ReadSwitches(const fn:string);
 
@@ -1229,7 +1229,10 @@ end;
 end.
 {
   $Log$
-  Revision 1.3  2001-08-29 23:31:27  pierre
+  Revision 1.4  2001-11-24 02:06:43  carl
+  * Renamed ppc.cfg -> fpc.cfg
+
+  Revision 1.3  2001/08/29 23:31:27  pierre
    * fix some m68k specific options
 
   Revision 1.2  2001/08/07 21:27:34  pierre

ide/readme.ide

@@ -61,7 +61,7 @@
  configuration changes before it can compile. This is due
  to the fact that the IDE includes its own compiler; it
  does not use ppc386.exe and thus it also does not use the
- configuration in the file ppc.cfg.
+ configuration in the file fpc.cfg.
 
  Select Target from the Compile menu and then check the
  correct default target (this is Go32V2 for DOS).

rtl/netware/README

@@ -68,8 +68,8 @@
     Settings and needed files to compile for netware
     ================================================
 
-    Edit your /etc/ppc386.cfg and add the rtl source path for netware. This are my settings,
-    you may paste it to your ppc386.cfg:
+    Edit your /etc/fpc.cfg and add the rtl source path for netware. This are my settings,
+    you may paste it to your fpc.cfg:
 
 #IFDEF Netware
   -Fu/usr/lib/fpc/1.1/units/netware/rtl

utils/fpcm/fpcmake.ini

@@ -809,7 +809,7 @@ override FPCOPT+=-gl
 override FPCOPTDEF+=DEBUG
 endif
 
-# Release mode (strip, optimize and don't load ppc.cfg)
+# Release mode (strip, optimize and don't load fpc.cfg)
 ifdef RELEASE
 ifeq ($(CPU_TARGET),i386)
 FPCCPUOPT:=-OG2p3