Closed raidgar98 closed 2 years ago
Looks like Doxygen 1.9.x breaks m.css. I see that 1.9.x generates a DoxyFile.xml
that m.css is unable to parse. I don't see the file in 1.8.x
and downgrading to 1.8.20 works.
ok i will downgrade doxygen to 1.8.x and retry running script
Had this problem, too. Another workaround that avoids downgrading can be to change the build process.
--no-doxygen
).Since m.css does not respect Doxyfile.xml, the absence of this file won't hurt. This worked for me.
Not really nice though if you are used to letting m.css call doxygen automatically!
As I understand, the XML processing of m-css does not just discard unexpected input files to proceed with the next but just fails and stops. I proposed a fix as #207.
Please fix this @mosra, the downgrade to doxygen 1.8.x doesn't work for me and the Doxyfile.xml deletion just isn't possible in my case. I like everything about this project and I wouldn't want to use an worse alternative :/
@crf8472 I've tried your solution (with removing step) and all i got is such error output.log
now i will try downgrading
in my case downgrading solves issue
@raidgar98 Glad to hear that downgrading helped!
If you are yet interested in inspecting the error you mentioned, I may take a look on that. It would help to have the input file that caused that error (conceptserek_1_1requirements_1_1detail_1_1fundamental__req.xml).
@crf8472 unfortunately i've removed it but i will reinstall to doxygen 1.9.* and will try to reproduce
@raidgar98 Glad to hear that downgrading helped!
If you are yet interested in inspecting the error you mentioned, I may take a look on that. It would help to have the input file that caused that error (conceptserek_1_1requirements_1_1detail_1_1fundamental__req.xml).
I get what I think is an equivalent error with this file. my assumption is that it has to do with the addition of concepts to both c++ and doxygen, and m.css hasn't yet handled generating docs for them
(running doxygen 1.9.3 and m.css@9385194)
Please bear with me, I'll look into this as soon as I adapt to changes that happened in various other dependencies (pygments, docutils, latex, graphviz, matplotlib, ...) during the past year so it passes at least the existing tests against the old 1.8 :sweat_smile:
I see Doxygen 1.9.3 being released a few days ago, so I'll try adapting directly to that. Hopefully it won't be as huge nightmare as all the previous versions, but I'm not holding my breath.
Finally fixed with a variant of #207, commited as 45911a188292a62b49ca4b226f590e9ca8cb75fa.
While the commit makes Doxygen 1.9 finally not blow up, please note the tool is not fully updated to it yet -- there's still about 10 test errors and 4 nasty assertions triggered by changes to the XML files. I still have to patch that up, which will be happening over the next days.
FYI for whoever is subscribed to this issue: #215 tracks remaining issues for proper Doxygen 1.9 support. Some of them are rather nasty (like the inline namespace regression), so until these boxes are all ticked off I don't recommend updating.
Hello, cannot find solution for this so i opening new one.
Here is my project: serek, and as you can see in workflows, CI passes with properly generated documentation: https://github.com/raidgar98/serek/actions/runs/1208747792
But if I try to create documentation same way locally, I got this error:
Following error occurs when parsing Doxygen.xml (I've printed it) I were 'workarounding' doxygen.py as long as script returned
0
. My work is avaiable in attached patchWorkflow enviroment is ubuntu 20.04, my setup is:
Does any of you have same problem? Can concepts be source of this problem?