Re: [Doxygen-users] How do I generate a single HTML file from just a marked-up comment?

[Kerry, R. <ric...@at...>]

Yes, \page is the answer to this.
And there is an index.html created as well as the file that I want.

> > > Doxygen to generate just one straightforward html file, and I don't
> > > seem to be getting any useful output.
> > >
> > > Doxygen will drop its additional "overhead" files into the output
> > > html directory, even if your .html file does not reference them.  It
> > > will include an index.html (even if it is basically empty), and some
> > > other .html files autogenerated.
> > [RK>] Though actually what I'm now getting is not what you describe.  I am
> getting an index.html file and no other .html files.
> > [RK>] so I must be missing something significant to persuade the system to
> generate some output form my comment.
> 
> index.html is created from a "\mainpage <title>" directive. If there is no
> \mainpage, then doxygen does some "default" thing. To generate some
> other page, then use "\page name <title>". This will create name.html.

[RK>] Ok, this is now fine.
[RK>] The \page directive is the key to getting arbitrary text in.
[RK>] And as you say, index.html is being created with some basic navigation stuff.

> > > That said, it should be possible to create a .html file you can copy
> > > out of Doxygen's output directory to your own web pages. 
> > > Doxygen will still drop some other random files in that directory
> > > that you will just ignore.

[RK>] And there is, as suggested, an index.html, which just links to all the other content.  So on using \page I get a specific html file generated, which I can easily extract, or link to.
 
> Try putting in a \page name Something in front of the markup. If the mark up
> is not part of some C/C++ thing (class, typedef, etc.) and not on the
> \mainpage [index.html] or a \page name [name.html] you might not get
> much or else with a lot of extrainious screen furniture. (There are also
> groups, but that will create a "Module", which you might not want.)  Using
> \page gets you something outside of a code oriented documentation (eg
> stuff related to code elements like classes or functions, etc.).

[RK>] Yes, \page was the key to getting this sorted.
[RK>] Although I think I have seen in the documentation a list that includes \class, \page, \file and others, I can't now find it.  Although I did find \page late yesterday afternoon it wasn't easy to find.  
[RK>] Regards,
[RK>] Richard.