summaryrefslogtreecommitdiffstats
path: root/doc/arch.doc
diff options
context:
space:
mode:
authorDimitri van Heesch <dimitri@stack.nl>2016-12-10 18:18:18 (GMT)
committerGitHub <noreply@github.com>2016-12-10 18:18:18 (GMT)
commit4474222932c6ff8bea64917ae1fb089a8390b5a8 (patch)
tree0da0fa2014569176bfd68ebb8f98697607d4f95e /doc/arch.doc
parent80656d68a0838483ea2988adf028e2d85292a109 (diff)
parentae033324fed6ff9b3febe12b5777f19c04e065d2 (diff)
downloadDoxygen-4474222932c6ff8bea64917ae1fb089a8390b5a8.zip
Doxygen-4474222932c6ff8bea64917ae1fb089a8390b5a8.tar.gz
Doxygen-4474222932c6ff8bea64917ae1fb089a8390b5a8.tar.bz2
Merge pull request #433 from albert-github/feature/docu_corr_433
Documentation small corrections
Diffstat (limited to 'doc/arch.doc')
-rw-r--r--doc/arch.doc8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/arch.doc b/doc/arch.doc
index 57d05d4..4b17d7c 100644
--- a/doc/arch.doc
+++ b/doc/arch.doc
@@ -188,7 +188,7 @@ could extract information from the XML output. Possible tools could be:
<h3>Debugging</h3>
Since doxygen uses a lot of \c flex code it is important to understand
-how \c flex works (for this one should read the man page)
+how \c flex works (for this one should read the \c man page)
and to understand what it is doing when \c flex is parsing some input.
Fortunately, when flex is used with the `-d` option it outputs what rules
matched. This makes it quite easy to follow what is going on for a
@@ -240,10 +240,10 @@ $now = time;
utime $now, $now, $file
\endverbatim
Another way to get rules matching / debugging information
-from the flex code is setting LEX_FLAGS with cmake.
+from the \c flex code is setting LEX_FLAGS with \c make (`make LEX_FLAGS=-d`).
-Note that by running doxygen with `-d lex` you get information about which flex
-codefile is used.
+Note that by running doxygen with `-d lex` you get information about which
+`flex codefile` is used.
\htmlonly
Return to the <a href="index.html">index</a>.