ALIASES = "\latexonly mytable=\\mytable \endlatexonly" ALIASES = "\\latexonly mytable=\\mytable \\endlatexonly" When googling before posting, I tested \latexonly. \_main_page.texĪdditional question : is there a way to not use doxygen.sty but really only mystyle.sty to avoid any kind of conflicts ? ~\doxygenLaTex\latex> grep usepackage refman.tex \_main_page.texīut not ~\doxygenLaTex\latex> more. ALIASES = problem seems to be I get this kind of things : ~\doxygenLaTex\latex> more. Tried a bit more stuffs, but did not work either : ~\doxygenLaTex> git diff I googled this and found Doxygen: include custom latex command or How to get Doxygen to recognize custom latex command which unfortunately didn't help me. # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-definedĭespite reading the doc, it didn't work: I get command as text ! Running doxygen cd latex make pdf AcroRd32.exe refman.pdf gives : So I look for how to use doxygen for that : ~\doxygenLaTex> lsĭoxyfile main.cpp mainpage.dox mystyle.sty I need to document this code : ~\doxygenLaTex> more main.cpp Doxygen - but are here for developers to identify this source file.How to use doxygen to produce a pdf with custom latex stylesheet and commands ? ClassTemplate provides an example of code documentation for the / Provide a description of this class memberĪnd the file src/ClassTemplate.cxx looks like Int Provide a description of this class member * and will inflate into the version, name, etc for this file. * Please note that the \$Header\$ keyword specified below is a RCS keyword, * form member groups preceded by a header as shown below. * and member variables to improve readability. * providing separate public, protected, private sections for member functions If the class has many members - you may consider Use standard C comments for those comments you wish * default constructors and destructors, should not be documented as this * Obvious member variables and functions, such as get and set routines and * to provide instructions to developers while writing their code. * Please remove comments that are bracketed by. * This comment block is required for all class declarations. This commenting system is illustrated in the Task Force Home Page for more information. See the Code Recommendations document on the Documentation You should include in standard C comments is a different matter, which is not treated Only deals with how the doxygen comments should be used the information that There are many ways in which you can choose to useĭoxygen comments to document your code. I shall use the Qt style for examples from now on,
0 Comments
Leave a Reply. |