Browse Source

* rename ppc386.cfg to ppc.cfg

carl 24 years ago
parent
commit
dd02c42009
3 changed files with 3 additions and 3 deletions
  1. 1 1
      ide/README
  2. 1 1
      ide/readme.ide
  3. 1 1
      utils/fpcm/fpcmake.ini

+ 1 - 1
ide/README

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

+ 1 - 1
ide/readme.ide

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

+ 1 - 1
utils/fpcm/fpcmake.ini

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