Introduction

This documentation is generated from the qucs sourcecode using Doxygen. Diagrams in the manual are produced by the dot utility–normally distributed as part of the graphviz package.

Hacking on this documentation

Eventually there will be a style guide for documenting, with an example of a one of the source files documented "by the book". Until then, feel free to start documenting or playing with doxygen configuration.

Doxygen Configuration

To edit the doxygen configuration, you can use (from the qucs-doc top directory):

• cd doxygen; doxywizard doxygen.cfg &

The default doxygen configuration only produces documentation for modules and data structures that have been explicitly tagged in the source code. More detailed documentation may be obtained by modifing the doxygen configuration file (.../doxygen/doxygen.cfg).

Options of particular interest include:

• INPUT which identifies the code to be scanned. The default configuration assumes that the qucs, qucs-core and qucs-doc top level directories are siblings.
• EXTRACT_ALL which will document all software components whether tagged or not.
• SOURCE_BROWSER which will embed implementation code in the documentation.

Enabling the latter two options will significantly increase the size of this manual, as well as the time it takes to generate it.

Doxygen reference documentation

The Doxygen web site (http://www.doxygen.org/) has a complete user manual. For the impatient, the most interesting sections are:

• How to write documentation blocks for files, functions, variables, etc.: http://www.doxygen.org/docblocks.html Be sure to include a file documentation block (@file or \file) at the top of your file. Without it your documentation will not appear in the html.
• List of the special commands you can use within your documentation blocks: http://www.doxygen.org/commands.html

Contacts

Web Site

News about Qucs as well as the latest version can always be found at the sourceforge project page http://qucs.sourceforge.net/

Email

If you have any suggestions concerning this documentation, do not hesitate to send suggestions to qucs-devel (see http://qucs.sourceforge.net/contact.html for details)

Author

Guilherme Brondani Torri (guito.nosp@m.rri@.nosp@m.gmail.nosp@m..com)