-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@see in enum element javadoc not rendering #77
Comments
|
Here we are running afoul of a couple of Doxygen issues and a Quickbook limitation. One of the Doxygen issues has a workaround. In enum tables, markup is not rendered without it (use one less space in the indent). See this comment for details. The other apparent Doxygen issue (new to me) is that, once the abovementioned workaround is in place, An obvious workaround for this is to additionally use Finally, the Quickbook limitation (I think): sections apparently do not render well in tables, hence this dumbing down: evanlenz@9d3644a#diff-d3ad2d9e6ee6aa89bed9e77741df133b5c92645d2906cf232ceeff35159d750aR44 When you remove one space from the indent and add This worked for me: /**
* A host is specified by IPv6address.
@see @ref ipv6_address
*/
ipv6, Any ideas as to what's different in the C++ between host_type and issue_63 that would make Doxygen fail to insert the reference (without an explicit |
You seem to be formatting the javadocs differently. I put the brief on the first line and I use 4 spaces for the indent:
|
Yeah, I understand. The workaround is to use fewer than four spaces on the indent for enums. I know this isn't ideal. See #63 for more examples with screenshots. Doxygen's HTML output had the same problem, so it's not unique to the XML output. |
well, if using fewer spaces solves the problem then I'm on board !!! is this possibly fixed in a newer doxygen? is there an open issue for it in their repo? |
I installed Doxygen 1.9.2 to test this. It looks like the issue is still there (interpreting the output as One (minor) drawback of the centralized docca.jam is that it isn't as immediately clear to me how you would run an HTML-output build (using otherwise the same Doxygen settings). @grisumbras Do you know of an easy way to do that? I used to just change the value from "XML" to "HTML" or something like that in the local Doxgyen settings file. Anyway, this would make it easy to determine if they've fixed this issue in the HTML output. |
I think you can change the library's Jamfile to do it? |
If you replace
with
and comment out all further targets that refer to reference.qbk, it should create doxygen HTML output. |
Excellent, thank you @grisumbras for that leg work! I think I might have done something wrong though. I'm getting:
Here are the edits I attempted to make to the beginning of the Jamfile: evanl@THINKPAD-T480 ~/boost/libs/url/doc
$ git diff .
diff --git a/doc/Jamfile b/doc/Jamfile
index 63828f6..3a51a4c 100644
--- a/doc/Jamfile
+++ b/doc/Jamfile
@@ -13,10 +13,12 @@ import boostbook ;
import os ;
import ../../../tools/docca/docca.jam ;
-docca.reference reference.qbk
- :
- xsl/custom-overrides.xsl
- [ glob-tree-ex ../include/boost/url : *.hpp *.ipp : detail impl ]
+import doxygen ;
+path-constant here : . ;
+local srcs = [ glob-ex $(here)/../include/boost/url : *.hpp *.ipp : detail impl ] ;
+srcs = $(here)/$(srcs) ;
+doxygen.doxygen reference.html
+ : $(srcs)
:
<doxygen:param>PROJECT_NAME=URL
<doxygen:param>PROJECT_BRIEF="URL Library" |
Oh, it's my mistake. Should be glob-tree-ex. The glob didn't find any sources, because it didn't consider subdirectories. |
Hmm, I got the same result after changing
(I don't know if it's related to me being on Cygwin or not.) Thanks again! |
@vinniefalco It looks like the problem persists in the latest version of Doxygen even in the HTML output: Also, I didn't find an obvious related issue in the Doxygen project. Should we file one? For now, it looks like we'll have to go with the smaller-indent workaround. That leaves open the question as to why Doxygen doesn't generate the reference from |
The text was updated successfully, but these errors were encountered: