> Yes, the main intent of Doxygen is to build documentation from the source
> code. You _can_ abuse it, however, to build documentation that isn't about
> the API. It may not be worth the trouble, but is an option. Instead, we
> could use a TCL script that asks for the available target types and
On Nov 4, 2008, at 8:14 AM, Øyvind Harboe wrote:
A thought in this direction is to use Doxygen to generate
documentation from
source code comments. It keeps the documentation close to the code
so it is
more likely to be up to date and the final output form can be
similar to
what we have
> A thought in this direction is to use Doxygen to generate documentation from
> source code comments. It keeps the documentation close to the code so it is
> more likely to be up to date and the final output form can be similar to
> what we have today. Some areas of the docs, like the getting st
On Nov 4, 2008, at 3:08 AM, Øyvind Harboe wrote:
I've committed the attached patch to get the ball rolling on how
we can make it easier to figure out what targets OpenOCD supports.
The general idea is that there should be a command which
will print in tabular form the supported CPUs and what o
I've committed the attached patch to get the ball rolling on how
we can make it easier to figure out what targets OpenOCD supports.
The general idea is that there should be a command which
will print in tabular form the supported CPUs and what options that should
be used so as to get the user star
