-
Notifications
You must be signed in to change notification settings - Fork 2k
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
doc: add RIOT root doxygen example path #17572
Conversation
I generally appreciate rendering more and more of what we have in documentation to where we advertise that our documentation is. The linked output currently has the markdown included as preformatted text rather than inlined and parsed. Why the split of doc.txt and README.md for the uwb? I think this would perfectly well as one file, given suitable markup. Similarly for the others: Why is this split into two files in the first place? |
As you can see with the UBW it previously was part of the doc.txt (empty README.md should be considered an achievement) (at the same time it was unrenderd) - (and the writer did not care or he like how it was more readable) .md files are much easier to write and to read that these .txt (personal opinion) README.MD further have the advantage that they are automaticaly render by github with doxygen 1.9.2 @include{doc} should work as it should (sandly with 1.9.1 it does not parse markdown -> generates an utter mess) https://doc.riot-os.org/group__pkg__uwb__dw1000.html |
.md files are much easier to write and to read that these .txt (personal opinion)
Yes, it gives syntax highlighting in most editors (for as good as it
gets with the markdown flavors and the extras added by doxygen).
README.MD further have the advantage that they are automaticaly render by github
Is it possible, with the recent Doxygen releases this needs, to use the
.md files for all our doc needs then? (Ie. also put the grouping stuff
in there). Having information spread (content vs structure) and
duplicated (title) between two files sounds suboptimal.
(I think we can afford having some Doxygen artifacts on the Github
rendering of the .md files).
|
at least a *.md wild card in doc/doxygen/riot.doxyfile:794 FILE_PATTERNS just remembering i also tested that it generated a smaller mess (but may be i used the doxygen grouping tags wrong) |
there isn't anything in that doc |
Is there an estimated release date for doxygen 1.9.2? Would it make sense to wait a little bit? |
And wouldn't #17575 be the preferred solution? |
?? "The latest version of doxygen is 1.9.3 (release date 31 december 2021, updated 3th of January 2022)." https://www.doxygen.nl/download.html#srcbin |
#17575 would be nice but it does not work as expected see #17572 (comment) , i am not sure if there is a doxygen version where that is fixed 1.9.2 (even 1.9.3) is already released but neither in our circleci nor is it used to build doc.riot-os.org
|
Sorry for the late response: apparently I've disabled too many of the GitHub notifications. Regarding the doxygen version: I was referring to the release of 1.9.2 as part of Debian. Even unstable still contains doxygen 1.9.1. Given the problem with #17575 I would agree with merging this PR for now and give #17575 another try once a newer doxygen version is available. |
Contribution description
add RIOT root to Doxygen example path
and include some Readme.md with their respective doc.txt
sadly we can't use
@includedoc
or@include{doc}
until Doxygen 1.9.2see doxygen/doxygen#8395
Testing procedure
read
and
check circleci: doc-build artifact
eg
https://15379-7370241-gh.circle-artifacts.com/0/doc/group__pkg__u8g2.html
vs
https://doc.riot-os.org/group__pkg__u8g2.html
Issues/PRs references
#10815