diff options
| author | dimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7> | 2000-11-05 19:00:55 (GMT) |
|---|---|---|
| committer | dimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7> | 2000-11-05 19:00:55 (GMT) |
| commit | 8b520502615f8fa68736d3e819c319a7f0594532 (patch) | |
| tree | 912d22a207a65d4bb3ea7b2082ae40a279f17dd0 /doc/external.doc | |
| parent | a6cc6b116194fc090532718fd4e1e0b22396052d (diff) | |
| download | Doxygen-8b520502615f8fa68736d3e819c319a7f0594532.zip Doxygen-8b520502615f8fa68736d3e819c319a7f0594532.tar.gz Doxygen-8b520502615f8fa68736d3e819c319a7f0594532.tar.bz2 | |
Release-1.2.3-20001105
Diffstat (limited to 'doc/external.doc')
| -rw-r--r-- | doc/external.doc | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/external.doc b/doc/external.doc index 01c275f..640768a 100644 --- a/doc/external.doc +++ b/doc/external.doc @@ -25,7 +25,7 @@ reasons to not include all sources for these with every run of doxygen: You may want to link to these pages instead of generating the documentation in your local output directory. <dt>Compilation speed:<dd> External projects typically have a different update - frequency form your own project. It does not make much sense to let doxygen + frequency from your own project. It does not make much sense to let doxygen parse the sources for these external project over and over again, even if nothing has changed. <dt>Memory:<dd> For very large source trees, letting doxygen parse all sources @@ -50,7 +50,7 @@ you should specify the name of the tag files after the \ref cfg_tagfiles "TAGFILES" option in the configuration file. A tag file does not contain information about where the external documentation -is located. This could be a directory or URL. So when you include a tag +is located. This could be a directory or an URL. So when you include a tag file you have to specify where the external documentation is located. There are two ways to do this: <dl> @@ -89,7 +89,7 @@ The directory structure looks as follows: \endverbatim \par -Then relevate parts of the configuration files look as follows: +Then the relevant parts of the configuration files look as follows: \par proj.cfg: \verbatim @@ -115,7 +115,7 @@ can use the \ref doxytag_usage "doxytag" tool to extract a tag file from the generated HTML sources. This tool depends on the particular structure of the generated output and on some special markers that are generated by doxygen. Since this type of extraction is brittle and error prone I -suggest to only use this approach if there is no alternative. The +suggest you to only use this approach if there is no alternative. The doxytag tool may even become obsolete in the future. \htmlonly |