[Doxygen-develop] Broken subpage links?

[Watts, S. (UK) <SW...@ng...>]

Hi all,

I am seeing broken subpage links in PDF/Latex output for a medium sized project.

Now, I have made a small test project in which these links *do* work, but I have not been able to deduce what would cause it to be failing in the "real" project...

The links are correctly formed in the HTML output, and the subpages can be reached from the main PDF navigation and contents page.  It appears to be _only_ the links from @subpage entries which are broken for PDF/Latex.

The links appear to be malformed in the raw tex output, as shown below.


Each page and its subpages are contained in their own '.dox' file, with a separate comment block for the page and each subpage, as shown in the following sample:

Sample source file:  "page-specifications.dox":
---------------------------------------------
/**	@page P0150overview Overview

	...blah...

	Topics covered:
	 - @subpage overview01 "Thingy"
	 - @subpage overview02 "Widget"
*/


/**	@page overview01 Tickling the Thingy
	
	...blah...
 */


/**	@page overview02 Winding the Widget

	...blah...
 */
---------------------------------------------

Tex output (snippet): ".../a00024.tex":
---------------------------------------------
	\begin{DoxyItemize}
	\item \hyperlink{a00025}{Thingy}	%< broken link
	\item \hyperlink{a00026}{Widget}	%< broken link
	\end{DoxyItemize}
	\hypertarget{overview01}{}     	%< first subpage target
	\section{Tickling the Thingy}
	\label{overview01}
	 ...
---------------------------------------------

NOTE: The broken links have names in the form "a%05d", sequentially following the filename.  There are also tex files in the latex output with these names (".../a00025.tex" etc), which are unrelated to this page and its subpages.


In addition (maybe related); the text in the pages (and subpages) mentions classes from the API being documented (as "Klass", "Klass::method()"), which I would expect to be auto-linked.  This is not happening, but such links are formed in the API documentation, and within code blocks (@code...@endcode, and @include) in these pages.




Any suggestions?


Simon./