Thursday, 10 November 2011

Eclipse fails to load & tool for Doxygen

I guess I've been lucky until now but I just had my first case of Eclipse failing to start. A quick googling found a solution. To recap:
  1. Close Eclipse.
  2. Backup & delete workspace/.metadata/.plugins/org.eclipse.core.resources.
  3. Start Eclipse.
  4. File -> Import -> Existing Projects into Workspace.
I created a rudimentary Python application to analyze quality of source commenting with Doxygen. The instructions are quite lacking and I'm sure there are lots of bugs left but maybe someone finds this useful? The idea is that the script gets two inputs: the log and index.xml files created by Doxygen. There are certain settings required for the Doxygen configuration for this to work.

The script will see which members have missing or incomplete documentation and will create an XML file that looks exactly like index.xml except for new attributes. This XML file can then be imported to e.g. Excel where one can use quick filters to calculate number of functions missing documentation etc.

DoxChecker is available from Gitorious.

P.S. My new computer (for  which I listed some test tools) is definitely much quieter than the old box thanks to a much better case (Fractal Design R3), lots of fans, a special cooler and a quietish video card. Not as quiet as my HTPC, mind, which is practially completely quiet thanks to the lack of a video card.

No comments:

Post a comment