Ah, now that the site’s back up, I searched for similar issues because I seemed 
to recall one relatively recently, and here it is: 
http://sourceforge.net/p/doxygen/mailman/message/32966735/.

But that thread was for the @mainpage tag in a file that (I think) had no 
extension, whereas I’d like to stick with the old *.page extension format.

So I modified the suggestion as follows, and now everything works again :-).

EXTENSION_MAPPING = page=C

-Monique

From: Monique Semp 
Sent: Monday, July 20, 2015 2:48 PM
To: doxygen-users 
Subject: no output for page/mainpage, v1.8.10, on OS X 10.10.3 (Yosemite)

Resending, now that the doxygen-users on SourceForge seems to have returned to 
online status.

Thanks for your help!
-Monique


From: Monique Semp 
Sent: Friday, July 17, 2015 11:48 AM
To: doxygen-users 
Subject: no output for page/mainpage, v1.8.10, on OS X 10.10.3 (Yosemite)

Hello, Doxygen users,

Does anyone know of any problems with the @mainpage and @page features in 
Doxygen 1.8.10, on OS X 10.10.3 (Yosemite)? I’m not getting any output for my 
.page files (and I’m not a Doxygen newbie; this has always worked, easily, as 
expected).

I’m explicitly including all my files (eight .h, the MainPage.page file for the 
@mainpage tag, and one @page file, TestPage.page) in the INPUT configuration 
options.

The .h files’ contents appear in the output as expected, but the .page files 
are not.

When I set both GENERATE_TREEVIEW and DISABLE_INDEX to YES, the right pane’s 
output does list “Main Page”, but its link is just the Doxygen output’s 
index.html page, without any of the content of the page file. When I return 
these config options to their defaults (NO), the resulting index.html page has 
no content. (The usual project info, etc. is shown, it’s just that the main 
pane where the .page file’s content should be is empty.)

I’ve tried lots of permutations in terms of the comment opener (/** and /*!) 
and the style for doxygen options (\ and @). But still no output for this very 
simple thing that I’ve done many, many times before.

But I’m just starting with a new project, and for the first time I’m using 
Doxygen 1.8.10 (my most recent project was with Doxygen 1.8.7), and OS X. (To 
date I’ve used previous Doxygen versions on Linux systems.) This is also my 
first time using the Doxygen Wizard. I’m editing the Doxyfile config file 
outside of the wizard, and reloading it into the Wizard before preforming any 
runs. I can’t see how this matters, but thought I should mention it.

So unfortunately, lots of possible issues: this version of Doxygen, how it 
works on OSX, and the wizard.

Thanks for any debugging tips,
-Monique

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Reply via email to