Thread: [Doxygen-users] Doxygen LaTeX output broken with MikTeX 2.9.7100
Brought to you by:
dimitri
From: Leonardo P. S. <Leo...@on...> - 2019-08-01 21:31:19
|
Hello All! Has anyone experienced problems with the LaTeX output and MikTeX 2.9.7100? When trying to generate the PDF output from the LaTeX output, I'm getting several errors like this: Missing } inserted. \end{DoxyEnumFields} The HTML output looks OK. I don't see any warnings when running Doxygen. I'm trying a VERY simple project componed of two source files, a header file and a source file. I'm using a fresh install of MikTeX 2.9.7100. Can anyone who was a LaTeX distributon installed give this example a go? This a showstopper for us. Thank you very much! Header file: /** * @file regular_c.h * @brief This is a simple C header file with some examples. */ #ifndef REGULAR_C_H_ #define REGULAR_C_H_ /* ---------------------------------------------------------------------------- * If building with a C++ compiler, make all of the definitions in this header * have a C binding. * ------------------------------------------------------------------------- */ #ifdef __cplusplus extern "C" { #endif /* ifdef __cplusplus */ /* ---------------------------------------------------------------------------- * Include files * --------------------------------------------------------------------------*/ /* ---------------------------------------------------------------------------- * Defines * --------------------------------------------------------------------------*/ /** Boolean true value */ #define TRUE 1 /** Boolean false value */ #define FALSE 0 /* ---------------------------------------------------------------------------- * Global variables and types * --------------------------------------------------------------------------*/ /** * This enumeration has the return codes for the @ref some_c_function function. */ enum SOME_C_FUNCTION_RETURN { SOME_C_FUNCTION_RETURN_everthing_ok = 0, ///< Nothing to see here SOME_C_FUNCTION_RETURN_some_weird_error, ///< This is not the error you're looking for SOME_C_FUNCTION_RETURN_some_very_bad_error, ///< This is not the error we are looking for SOME_C_FUNCTION_RETURN_life_is_sad_just_cope ///< Move along }; /** * @brief Some C function that is here just as an example. * * This function doesn't actually do anything useful. We just use to have some * documentation that links back to a Markdown source file * * @param[in] v We do something with this value. * @param[out] ptr Some value will be written here. * * @return Returns a value that depends on what happened: * - @ref SOME_C_FUNCTION_RETURN_everthing_ok * Uh, everything is under control. Situation normal. * - @ref SOME_C_FUNCTION_RETURN_some_weird_error * Uh, had a slight weapons malfunction. * - @ref SOME_C_FUNCTION_RETURN_some_very_bad_error * We had a reactor leak here now. Give us a few minutes to lock it down. * Large leak... very dangerous. * - @ref SOME_C_FUNCTION_RETURN_life_is_sad_just_cope * Who is this?? What's your operating number? * * @see SOME_C_FUNCTION_RETURN */ int some_c_function(uint32_t v, void* ptr); /* ---------------------------------------------------------------------------- * Close the 'extern "C"' block * ------------------------------------------------------------------------- */ #ifdef __cplusplus } #endif /* ifdef __cplusplus */ #endif /* REGULAR_C_H_ */ Source File: /** * @file regular_c.c * @brief This is a simple C source file with some examples. The functions are * documented in the header file. */ #include "regular_c.h" int some_c_function(uint32_t v, void* ptr) { switch(v) { /* Not a real case, just using some enum */ case SOME_C_FUNCTION_RETURN_everthing_ok: *((uint8_t*)ptr) = v*v; break; case SOME_C_FUNCTION_RETURN_some_weird_error: *((uint8_t*)ptr) = -1; break; case SOME_C_FUNCTION_RETURN_some_very_bad_error: *((uint8_t*)ptr) = -2; break; case SOME_C_FUNCTION_RETURN_life_is_sad_just_cope: *((uint8_t*)ptr) = 0; break; } return SOME_C_FUNCTION_RETURN_everthing_ok; } Doxyfile # General options PROJECT_NAME = "Doxygen" INPUT = src/regular_c.c include/regular_c.h OUTPUT_DIRECTORY = output_doc ____________________________________________________________ Leonardo Pereira Santos | ON Semiconductor Design Engineer 200-611 Kumpf Dr | Waterloo, Ontario, Canada, N2N 1A8 519-884-9696 x2269 (O) | Leo...@on...<mailto:Leo...@on...> |
From: Paolo G. <pj...@ev...> - 2019-08-02 05:16:57
|
Dear Leonardo, > Has anyone experienced problems with the LaTeX output and MikTeX > 2.9.7100? When trying to generate the PDF output from the LaTeX output, > I’m getting several errors like this:[...] We had a similar issue, please see this message: https://sourceforge.net/p/doxygen/mailman/message/36523775/ It seems that miktex has a newer version of the longtabu package than Ubuntu. Please check of the problem you have is also linked to the usage of the longtabu package or if it is due to something else. Ciao, PJ |
From: Leonardo P. S. <Leo...@on...> - 2019-08-02 20:34:39
|
Paolo, Thank you for your reply. Turns out, it was (obviously) my fault. \uppercase{\chaptertitlename} Need braces. And you should not use it anyway. Using \MakeUppercase solves my problems. https://tex.stackexchange.com/questions/502570/error-with-uppercase-in-titlesecs-label-field/502572#502572 Thanks again! -----Original Message----- From: Paolo Gai [mailto:pj...@ev...] Sent: August-02-19 12:53 AM To: Leonardo Pereira Santos <Leo...@on...>; dox...@li... Subject: Re: [Doxygen-users] Doxygen LaTeX output broken with MikTeX 2.9.7100 [External Email]: This email arrived from an external source - Please exercise caution when opening any attachments or clicking on links. Dear Leonardo, > Has anyone experienced problems with the LaTeX output and MikTeX > 2.9.7100? When trying to generate the PDF output from the LaTeX output, > I'm getting several errors like this:[...] We had a similar issue, please see this message: https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceforge.net_p_doxygen_mailman_message_36523775_&d=DwID-g&c=MHZppzMdXMt3JYjCV71UsQ&r=k8KpFgIlnqWJ_UCMIorh7Kaa71fn5J46EO16Eh-Dgx5RVhccwhWRNbrzEpx0RhhR&m=PnT9U86Nrr0kAnImSZ2Q_jCYfj1NwYoI_RBPgG0hlys&s=k20Wk-STL0q4axuAnZDyG9qwIYWDmRd4hxCAVWYN9V4&e= It seems that miktex has a newer version of the longtabu package than Ubuntu. Please check of the problem you have is also linked to the usage of the longtabu package or if it is due to something else. Ciao, PJ |