Doxygen parsing of .nut files


#1

I’ve noticed that the eImp libraries are properly decorated with doxygen comments.
I’ve been trying myself to get doxygen to properly parse one of my own libraries, to no avail. I got it to process the .nut file(s) but the output is more or less empty, no matter what source type (squirrel is not build in) I ask it to assume.

Any advice on how to make it work ?

  • doxygen configuration settings
  • pre-parser ?
  • extension mapping ?


#2

We started unifying the library code comments. It’s JSONDoc that we decided to follow. There is no publicly documented process of generating documentation from the source codes yet. But we’ll continue moving in this direction to make it publicly available so that everyone can benefit from it.