Hi,
A third party vendor (Microsemi) has inserted doxygen documentation into
their provided source code.
Problem is just that they have chosen to use @mainpage in each and every
main header file.
When I run doxygen on the source hierarchy, doxygen picks the first
@mainpage and uses that, the rest is ignored. I understand from a google
search that this is the way things work.
I have prevented the above behaviour by creating my own mainpage.dox file
and put the location of that file in front of the Microsemi code in INPUT:
INPUT = . path/to/third_party_code
Now, I have full control over the @mainpage, but I actually wanted to
collect all the documentation Microsemi has provided in their header files.
As an experiment, I modified a few of the Microsemi headerfiles to use
@page instead of @mainpage. Now, the documentation shows up in the
navigation bar. Problem is just that @page "steals" the first word in the
title to use for page name. By inserting a unique filename I can fix this,
too.
The problem is that this is third party driver code for a Cortex-M3 CPU,
and every time I generate the support package, the source code is
regenerated, overwriting any manual changes I do in the files. I also don't
expect Microsemi to change their code.
Is there a way to do on-the-fly change of @mainpage title to @page
<base_name> title after having picked up the first @mainpage which I
provide in my mainpage.dox file?
--
Svenn
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
