[Gtkradiant] Re: Doxygen Patch
Timothee Besset
gtkradiant@zerowing.idsoftware.com
Sat, 18 Aug 2001 11:13:33 +0200
That looks very promising! And it's got a whole bunch of info .. definitely something we will want to have working on zerowing soon.
A few things though:
I'm not sure about how the "target" system should work. Just doing one directory might not be enough. Maybe we should just hardcode it .. or allow several directories .. the interesting stuff would be to have radiant/ include/ and libs/, or only include/ for plugin/module writers
Prolly need to be able to specify the output directory too
I had some weird stuff when applying the patch .. maybe I should have done -p1
I dunno on top of which source tree it was built, but it seemed to conflict a bit with existing doxygen files in the tree. Ended up copying stuff from old/ back into the new tree.
TTimo
timo@antares:~/Id/GtkRadiant-IMap$ bzip2 -dc doxy.patch.bz2 | patch -p0
patching file old/DoxyConfig
The next patch would delete the file new/Doxygen_extras/CVS/Entries,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/Doxygen_extras/CVS/Repository,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/Doxygen_extras/CVS/Root,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/Doxygen_extras/CVS/Tag,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file old/Doxygen_files/Doxyfile
patching file old/Doxygen_files/doxy_mainpage.h
patching file old/Doxygen_files/doxygen_gtkradiant.css
patching file old/Doxygen_files/doxygen_gtkradiant_foot.html
patching file old/Doxygen_files/doxygen_gtkradiant_head.html
patching file old/Doxygen_files/doxygen_index.html
patching file old/Doxygen_files/doxygen_reference_foot.html
patching file old/Doxygen_files/doxygen_reference_head.html
patching file old/Doxygen_files/example/annotated.html
patching file old/Doxygen_files/example/classIEpair-members.html
patching file old/Doxygen_files/example/classIEpair.html
patching file old/Doxygen_files/example/classes.html
patching file old/Doxygen_files/example/doxygen.gif
patching file old/Doxygen_files/example/doxygen_gtkradiant.css
patching file old/Doxygen_files/example/files.html
patching file old/Doxygen_files/example/functions.html
patching file old/Doxygen_files/example/graph_legend.dot
patching file old/Doxygen_files/example/graph_legend.gif
patching file old/Doxygen_files/example/graph_legend.html
patching file old/Doxygen_files/example/index.html
patching file old/Doxygen_files/example/pages.html
patching file old/Doxygen_files/example/test_8c-source.html
patching file old/Doxygen_files/example/test_8c.html
patching file old/Doxygen_files/example/todo.html
patching file old/Doxygen_files/genConf
patching file old/Doxygen_files/genDoxyfile
patching file old/Doxygen_files/gendoxfunctions
patching file old/Doxygen_files/images/body-left-tile.gif
patching file old/Doxygen_files/images/body-lower-left.gif
patching file old/Doxygen_files/images/body-lower-right.gif
patching file old/Doxygen_files/images/body-lower-tile.gif
patching file old/Doxygen_files/images/body-right-tile.gif
patching file old/Doxygen_files/images/body-upper-left.gif
patching file old/Doxygen_files/images/body-upper-right.gif
patching file old/Doxygen_files/images/body-upper-tile.gif
patching file old/Doxygen_files/images/gtkr_splash.jpg
patching file old/Doxygen_files/images/gtkr_splash_sm.jpg
patching file old/Doxygen_files/images/history_id_logo.gif
patching file old/Doxygen_files/images/top-right.gif
patching file old/Doxygen_files/images/top-tile.gif
patching file old/Doxygen_files/images/top-title.gif
patching file old/Doxygen_files/reference1.html
patching file old/README.doxygen
The next patch would delete the file new/doxygen-out/CVS/Entries,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/doxygen-out/CVS/Entries.Log,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/doxygen-out/CVS/Repository,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/doxygen-out/CVS/Root,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/doxygen-out/CVS/Tag,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/doxygen-out/images/CVS/Entries,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/doxygen-out/images/CVS/Repository,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/doxygen-out/images/CVS/Root,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
The next patch would delete the file new/doxygen-out/images/CVS/Tag,
which does not exist! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
patching file old/gendox
On Thu, 16 Aug 2001 12:23:11 +1000
Geoff Davis <gefdavis@dingoblue.net.au> wrote:
> TTimo,
>
> I've added a bunch of stuff to generate the doxygen documentation via a script.
> "GtkRadiant/gendox"
> The script will set the options for the perl path, dot path, have dot, output language,
> project name and the project version. And then run doxygen on the generated
> config file.
>
> I've also added links and a little info to the main index page, and a quick reference
> to doxygen style documentation.
>
> The script is called with a target (eg: sh gendox ./include) and outputs the documentation
> to '../GtkRadiant-doxygen', which is outside of the cvs dir. If the script isn't passed
> a target, it will look for a radiant dir, and generate the docs from that.
>
> The patch included is bzipped. To apply it: 'bzip2 -dc doxy.patch | patch -p0'
>
> Any additions or changes you need, let me know
>
> Gef :]