-
Notifications
You must be signed in to change notification settings - Fork 202
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
Fix #559, Resolve doxygen warnings #648
Fix #559, Resolve doxygen warnings #648
Conversation
fsw/cfe-core/src/inc/cfe_sb.h
Outdated
@@ -562,7 +560,7 @@ int32 CFE_SB_UnsubscribeLocal(CFE_SB_MsgId_t MsgId, CFE_SB_PipeId_t PipeId); | |||
** | |||
** \param[in] MsgPtr A pointer to the message to be sent. This must point | |||
** to the first byte of the software bus message header | |||
** (#CFE_SB_Msg_t). | |||
** ("::"CFE_SB_Msg_t). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious why old reference didn't work? What does "::"
do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Part of the autolink system: http://www.doxygen.nl/manual/autolink.html (item 3 under "Links to functions"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I double checked, I'm noticing that the literal "::" appears as well. I missed that, I may need to revisit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did the #
cause an error/warning? Note 3 from that reference seems to say #
should work? "For Javadoc compatibility a # may be used instead of a :: in the patterns above."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was, yes, which is why I changed it, and got no error as a result.
fsw/cfe-core/src/inc/cfe_sb.h
Outdated
@@ -595,7 +593,7 @@ int32 CFE_SB_SendMsg(CFE_SB_Msg_t *MsgPtr); | |||
** | |||
** \param[in] MsgPtr A pointer to the message to be sent. This must point | |||
** to the first byte of the software bus message header | |||
** (#CFE_SB_Msg_t). | |||
** ("::"CFE_SB_Msg_t). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above.
fsw/cfe-core/src/inc/cfe_sb_msg.h
Outdated
@@ -54,7 +54,7 @@ | |||
** \cfecmdmnemonic \SB_NOOP | |||
** | |||
** \par Command Structure | |||
** #CFE_SB_CmdHdr_t | |||
** cfe_sb.h::CFE_SB_CmdHdr_t |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do these show up as links? Curious why old reference didn't work
fsw/cfe-core/src/sb/cfe_sb_priv.h
Outdated
@@ -413,18 +413,16 @@ int32 CFE_SB_RemoveDest(CFE_SB_RouteEntry_t *RouteEntry, CFE_SB_DestinationD_t * | |||
** | |||
** \par Assumptions, External Events, and Notes: | |||
** - For statically defined messages, a function call will not work. The | |||
** macros #CFE_SB_CMD_HDR_SIZE and #CFE_SB_TLM_HDR_SIZE are available for use | |||
** macros cfe_sb.h::CFE_SB_CMD_HDR_SIZE and cfe_sb.h::CFE_SB_TLM_HDR_SIZE are available for use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do these link correctly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are not working, I missed them too. Will fix
@@ -2,12 +2,7 @@ | |||
# Project related configuration options, shared for all cFE doxygen outputs | |||
#--------------------------------------------------------------------------- | |||
@INCLUDE_PATH = @MISSION_SOURCE_DIR@ | |||
DOXYFILE_ENCODING = UTF-8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were all deleted settings the defaults?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where can a user go find what the defaults are?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doxygen will create a config file with the defaults, doxygen -g configfile
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be worthwhile to add a comment that says "to see defaults run doxygen -g configfile" ?
As we experienced last week, doxygen knowledge is sparse, and this might help.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's on the man page...
I guess I missed a few of these. I thought they were working. I will need to revisit and push a fix |
@lbleier-GSFC I like the simplification. Can you post a built version of this so we can see how these changes will affect the generated doc? |
When it's ready go ahead and tag with the "ready for CCB" label |
I am not quite sure what you're asking for. The entire documentation? Where would I post it? |
Likely just the pdf that gets built from the latex directory. |
Drag and drop to add it to a comment here |
Latex doesn't get generated, as per the config file. I don't see any relevant PDFs |
I wonder why we don't for doc, we do for osalguide and usersguide. Want to try enabling it and see if you can build the pdf? Enable latex, enter the build/doc/detaildesign/latex directory and type make, if it works it'll create a refman.pdf (or whatever name it's set to) which can be dropped here. |
I am trying to build but it's failing, I'll need to investigate |
I managed to build a PDF despite a ton of warnings and File: |
CCB-20200506 - APPROVED, Open new tickets for LaTeX mission docs and missing function documentation. |
@skliper @lbleier-GSFC did we open tickets for these? |
Yes, #682 and #681, looks like the latter has already been fixed in #686 |
@lbleier-GSFC can you resolve these conflicts? |
I'm not quite sure what the conflict is. Both the |
I recommend rebasing your changes on top of IC, and resolve conflicts there. |
Also needs squash |
894e6e0
to
b58ff99
Compare
@astrogeco - Resolved and squashed. |
Fix nasa#559, Resolve doxygen warnings
Describe the contribution
Fixes #559, resolving all doxygen warnings
Testing performed
Steps taken to test the contribution:
warnings.log
make doc
Expected behavior changes
A clear and concise description of how this contribution will change behavior and level of impact.
Contributor Info - All information REQUIRED for consideration of pull request
Full name and company/organization/center of all contributors ("Personal" if individual work)