-
Notifications
You must be signed in to change notification settings - Fork 3k
Doxygen template and CI to not produce warnings and errors #4425
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
Conversation
cf4a809
to
b54902e
Compare
Starting from the top of the list with RTOS. @deepikabhavnani said she could start from the center and we'll work towards each other. |
I'll start from the bottom, once I get the CI work done. |
Please be aware: I'm currently modifying history. |
4ad1b1b
to
727f52f
Compare
I'm done editing history. This travis build should pass and tests for no warnings in the doxygen! |
Taking up Frameworks next, Deepika is on Filesystems. |
Should be kept in sync with doxygen_options.json which is used for building the doxygen which is used by docs.mbed.com It is intended only generate doxygen for specific directories which present the public APIs for mbed OS
looks like a regression in doxygen happened recently in platform. |
Description
To verify the doxygen documentation is compatible with the developer.mbed.org and docs.mbed.com doxygen_options can be used
doxygen doxygen_options
to build locally. When modifications are made to this file they must also be made todoxygen_options.json
Only a subset of options are available in
doxygen_options.json
therefore should not depend on modifications to options that are not present.@theotherjimmy tbd add to travis and verify output is clean (ie no warnings or errors)
Additional commits to fix additional warnings added in the last few days since the platform/* directory was last warning free.
Status
READY
Todos
Directories still needing errors and warnings to be fixed: