libftdi Archives
|
From: | Dan White <dan@xxxxxxxxxxxxxx> |
---|---|
To: | libftdi@xxxxxxxxxxxxxxxxxxxxxxx |
Date: | Wed, 31 Oct 2012 23:11:58 -0500 |
On Mon, Oct 29, 2012 at 4:28 AM, xantares 09 <xantares09@xxxxxxxxxxx> wrote:
Thanks for the review! My lack of cmake fu is apparent. The updated patch set should take care of most of the comments.
Done.
Done. Splitting the xml generation out as a separate step was the trick.
Done.
The combination of setting %feature("autodoc","1"); and the doxy2swig.py -n option to not output prototypes works well. Disagreements then show up in the "Returns:" section of the docstring, but that is direct from the doxygen comments.
It doesn't seem to be, I'm sure there are lots of projects using the swig/doxy combination who would be happy to not use their ad-hoc setups to avoid twice-documenting the exported functions.
The commits also live on github on my "doxygen-swig" branch Dan SDG www.whiteaudio.com libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
0001-Enable-separate-doxygen-XML-output.patch
0002-Extract-doxygen-from-ftdi.c-to-python-docstrings.patch
0003-Tweak-doxy2swig.py-output-to-include-Returns-header.patch |
Current Thread |
---|
|