From 98a378b9634be81374877384bc0872431c01bee3 Mon Sep 17 00:00:00 2001
From: "ol.sc" <ol.sc@b7a2c559-68d2-44c3-8de9-860c34a00d81>
Date: Tue, 27 Dec 2011 15:30:34 +0000
Subject: [PATCH] - Removed -f option. - Replaced references to target 'geos'
 with references to (the to-be renamed) 'cbm-geos'.

git-svn-id: svn://svn.cc65.org/cc65/trunk@5325 b7a2c559-68d2-44c3-8de9-860c34a00d81
---
 doc/grc65.sgml | 27 +++++++++++----------------
 1 file changed, 11 insertions(+), 16 deletions(-)

diff --git a/doc/grc65.sgml b/doc/grc65.sgml
index dcd009ad9..2c7cb6d7a 100644
--- a/doc/grc65.sgml
+++ b/doc/grc65.sgml
@@ -40,16 +40,11 @@ should be processed by <bf/ca65/ and linked to the application (read about
 <sect>Usage
 <p>grc65 accepts the following options:<tscreen><verb>
 -h, -?     this help
--f         force writing files
 -o name    name the C output file
 -s name    name the asm output file
 </verb></tscreen>
 Default output names are made from input names with extensions replaced by
-<tt/.h/ and <tt/.s/.  <bf/grc65/ will not overwrite existing files unless forced
-to do so.  That is done to avoid situations where you have <tt/test.c/ and
-<tt/test.grc/ files.  Both would put their output into <tt/test.s/.  For that
-reason, you should name your resource-files differently than sources, e.g.,
-<tt/resource.grc/ or <tt/apphead.grc/.
+<tt/.h/ and <tt/.s/.
 
 
 
@@ -207,21 +202,21 @@ Note that &dquot;<tt/resource.h/&dquot; is included at the top of
 
 <sect2>Second step -- assembling the application header
 <p><verb>
-$ ca65 -t geos resource.s
+$ ca65 -t cbm-geos resource.s
 </verb>
 And, voil&aacute; -- &dquot;<tt/resource.o/&dquot; is ready.
 
 <sect2>Third step -- compiling the code
 <p><verb>
-$ cc65 -t geos -O test.c
-$ ca65 -t geos test.s
+$ cc65 -t cbm-geos -O test.c
+$ ca65 -t cbm-geos test.s
 </verb>
 That way, you have a &dquot;<tt/test.o/&dquot; object file which
 contains all of the executable code.
 
 <sect2>Fourth and last step -- linking it together
 <p><verb>
-$ ld65 -o test.cvt -t geos resource.o geos.o test.o geos.lib
+$ ld65 -o test.cvt -t cbm-geos resource.o geos.o test.o geos.lib
 </verb>
 &dquot;<tt/resource.o/&dquot; comes first because it contains the
 header.  The next one is &dquot;<tt/geos.o/&dquot;, a required starter-code
@@ -233,7 +228,7 @@ contained in the well-known GEOS <em/Convert/ format.  Note that its name
 (<tt/test/) isn't important; the real name, after deconverting, is the DOS name
 that was given in the header definition.
 
-At each step, a <tt/-t geos/ was present on the command-line.  That switch is
+At each step, a <tt/-t cbm-geos/ was present on the command-line.  That switch is
 required for the correct process of GEOS sequential app. building.
 
 
@@ -267,13 +262,13 @@ Now, there are two new files:  &dquot;<tt/cvthead.cfg/&dquot; and
 &dquot;<tt/cvthead.s/&dquot; -- the first one is a config. file for <bf/ld65/,
 and the second one contains the GEOS <tt/.cvt/ header.  It can be assembled:
 <verb>
-$ ca65 -t geos cvthead.s
+$ ca65 -t cbm-geos cvthead.s
 </verb>
 Now, we have &dquot;<tt/cvthead.o/&dquot;.  The rest of the assembly
 sources can be assembled:<verb>
-$ ca65 -t geos vlir0.s
-$ ca65 -t geos vlir1.s
-$ ca65 -t geos vlir2.s
+$ ca65 -t cbm-geos vlir0.s
+$ ca65 -t cbm-geos vlir1.s
+$ ca65 -t cbm-geos vlir2.s
 </verb>
 Note that the file-names here, although similar to those from the
 <tt/VLIR/ section of the <tt/.grc/ file, are not significant.  The only thing
@@ -294,7 +289,7 @@ $ grc65 -vlir output.cvt vlir-head.bin vlir-0.bin vlir-1.bin vlir-2.bin
 </verb>
 That is the end.  The file &dquot;<tt/output.cvt/&dquot; can be
 deconverted under GEOS.  Note that <tt/-C cvthead.cfg/ was used on the
-<bf/ld65/ command-line instead of the switch <tt/-t geos/.
+<bf/ld65/ command-line instead of the switch <tt/-t cbm-geos/.
 
 
 
-- 
2.39.5