You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running sphinx-build (5.3) with sphinxcontrib.doxylink (1.12.2) added on a doxygen XML generated with doxygen 1.9.7, I get the following errors in the build.
Example 1: the same local definition, but different
Extension error (sphinxcontrib.doxylink.doxylink):
Handler <function setup_doxylink_roles at 0x7f57602343a0> for event 'builder-inited' threw an exception (exception: Cannot add override to non-function 'msr::g_stopWatch')
I can't post the full example because the project is huge (and proprietary), so maybe could you give a few hints for which things to look out first?
The symbol that sphinx complains about is a global variable in two files:
When running sphinx-build (5.3) with sphinxcontrib.doxylink (1.12.2) added on a doxygen XML generated with doxygen 1.9.7, I get the following errors in the build.
Example 1: the same local definition, but different
I can't post the full example because the project is huge (and proprietary), so maybe could you give a few hints for which things to look out first?
The symbol that sphinx complains about is a global variable in two files:
second cpp file:
The doxygen.tag file contains the symbol 4 times:
I think it is a problem of doxygen that it adds the variable with initalizer value as a function. Anyhow, would it be possible to catch this gently?
Example 2: Overriding #define
The same problem occurs in other kinds of "double definition by doxygen" situations, like:
Doxygen XML:
Doxylink error:
None of that code is nice, but I'd argue that this code exists and C/C++ builds it, so it should not lead to a crash of sphinxcontrib.doxylink.
Example 3: SFINAE
Here, I have totally valid C++ SFINAE template code that causes the dreaded error again:
The C++ code (header file):
Doxygen gets the last one wrong:
The text was updated successfully, but these errors were encountered: