Doxygen failed about maplab HOT 3 CLOSED

Hi @qinyusen
I'm afraid we don't have a lot of experience with doxygen in our team and maplab doesn't really use the doxygen comment style. However having a doxygen page would definitely be helpful, even without the comments, so if you are pursuing this we would of course appreciate it if you share the results with us.

The only thing I could think of is that maplab is a metapackage and that's why it's not working. Sorry for not being more helpful.

from maplab.

Hi, @mfehr

It's ok, I will look forward to try to make it works. And will ask for a merge request if I have a solution.

Since doxygen could simply show how funtions called even no doxygen style commit , and also for maplab such a modularization project, a call graph will really help people to understand it.

And as a engineer in Segway Robotics, I just curious on how your team works for such a big project and make the debug?

BR,
Yusen

from maplab.

@qinyusen
To navigate through the code, we mostly rely on our IDEs (e.g. Eclipse) that help to understand types and function signatures. We also try to name function/parameters so the code is as self-explanatory as possible.

For the debugging, we mostly rely on Google Logging Library by adding checks whenever possible (so you know where your code crashed -> it's easy to identify the bug). Additionally, unit tests and a continuous integration server helps to detect errors when changing the codebase.

from maplab.