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
clean up doxygen errors introduced by new metaprograms #1793
Comments
Things are a bit better now:
|
Current status:
|
Updating my local doxygen version to
|
Thats odd, it should be failing on develop since I switched the flag to fail for warnings |
I'm not seeing any errors locally
Can you try running |
Yay for differences in versions! (That was sarcastic.) I’ll try that.
…On Fri, May 8, 2020 at 12:46 PM Steve Bronder ***@***.***> wrote:
I'm not seeing any errors locally
make doxygen
mkdir -p doc/api
doxygen doxygen/doxygen.cfg
doxygen -v
1.8.13
Can you try running make clean-all then make doxygen? Should we update
doxygen on jenkins? I'm guessing newer versions are catching this while
older versions let is slide
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1793 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADH6F7NKBH3GMOCVJ6ETADRQQZO7ANCNFSM4LSAN3KQ>
.
|
lol ty, if that fails maybe it's just EOL for the doxygen version on jenkins and we should upgrade |
Description
The new metaprograms introduced recently introduced a host of doxygen warnings:
The symbol
m1
doesn't even show up in that file. There are also lots of problems with scalars. In total:Current Version:
v3.1.0
The text was updated successfully, but these errors were encountered: