summaryrefslogtreecommitdiffhomepage
path: root/doc/mdk_gstart.texi
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2004-08-01 21:43:29 +0000
committerJose Antonio Ortega Ruiz <jao@gnu.org>2004-08-01 21:43:29 +0000
commit9f985f28b2e1bfdbbf871ab56280fffdb876eee6 (patch)
tree6cdee8944ce4a6a21b77e49df2f7c8f149bd4040 /doc/mdk_gstart.texi
parent46a7303934d2a26623620e26771023efc4fbf208 (diff)
downloadmdk-9f985f28b2e1bfdbbf871ab56280fffdb876eee6.tar.gz
mdk-9f985f28b2e1bfdbbf871ab56280fffdb876eee6.tar.bz2
document mixasm -O option and delete references to -g.
Diffstat (limited to 'doc/mdk_gstart.texi')
-rw-r--r--doc/mdk_gstart.texi25
1 files changed, 13 insertions, 12 deletions
diff --git a/doc/mdk_gstart.texi b/doc/mdk_gstart.texi
index 10302d4..9eab3f6 100644
--- a/doc/mdk_gstart.texi
+++ b/doc/mdk_gstart.texi
@@ -1,10 +1,10 @@
@c -*-texinfo-*-
@c This is part of the GNU MDK Reference Manual.
-@c Copyright (C) 2000, 2001, 2002, 2003
+@c Copyright (C) 2000, 2001, 2002, 2003, 2004
@c Free Software Foundation, Inc.
@c See the file mdk.texi for copying conditions.
-@c $Id: mdk_gstart.texi,v 1.16 2003/06/09 15:18:11 jao Exp $
+@c $Id: mdk_gstart.texi,v 1.17 2004/08/01 21:43:29 jao Exp $
@node Getting started, Emacs tools, MIX and MIXAL tutorial, Top
@chapter Getting started
@@ -116,17 +116,18 @@ the @file{hello.mixal} file, you can type the following command at your
shell prompt:
@example
-mixasm -g hello @key{RET}
+mixasm hello @key{RET}
@end example
@cindex .mix file
If the source file contains no errors, this will produce a binary file
called @file{hello.mix} which can be loaded and run by the MIX virtual
-machine. The @code{-g} flag tells the assembler to include debug
-information in the executable file (for a complete description of all
-the compilation options, see @ref{mixasm}). Now, your are ready to run
-your first MIX program, as described in the following section.
+machine. Unless the @code{mixasm} option @code{-O} is provided, the
+assembler will include debug information in the executable file (for a
+complete description of all the compilation options, see
+@ref{mixasm}). Now, your are ready to run your first MIX program, as
+described in the following section.
@node Running the program, Using mixguile, Compiling, Getting started
@@ -459,11 +460,11 @@ MIX >
@cindex @code{sbp}
@cindex breakpoints
@noindent
-Note that, since we compiled @file{hello.mixal} with debug info enabled
-(the @code{-g} flag of @code{mixasm}), the virtual machine is able to
-tell us the line in the source file corresponding to the breakpoint we
-are setting. As a matter of fact, you can directly set breakpoints at
-source code lines using the command @code{sbp LINE_NO}, e.g.
+Note that, since we compiled @file{hello.mixal} with debug info
+enabled, the virtual machine is able to tell us the line in the
+source file corresponding to the breakpoint we are setting. As a
+matter of fact, you can directly set breakpoints at source code lines
+using the command @code{sbp LINE_NO}, e.g.
@example
MIX > sbp 4