By Petr Zemek (8. August 2007, 19:13:57)
Re: Compiling without warnings issues
 (2 )

Hi Peter,
thanks for that link! Now I see that it should be possible to expand these macros to make the docs complete and that’s what we actually want.

I’ve tried this (and some other combinations as well) configuration, but it doesn’t work and I don’t know why…

#---------------------------------------------------------------------------
# Configuration options related to the preprocessor
#---------------------------------------------------------------------------
ENABLE_PREPROCESSING = YES
MACRO_EXPANSION = YES
EXPAND_ONLY_PREDEF = YES
SEARCH_INCLUDES = YES
INCLUDE_PATH =
INCLUDE_FILE_PATTERNS =
PREDEFINED =
EXPAND_AS_DEFINED = REFERENCE_OBJECT \
VALUE_OBJECT \
STATIC_HELPER
SKIP_FUNCTION_MACROS = NO

The output still doesn’t contain expanded macros, even if I set EXPAND_ONLY_PREDEF to NO and omit the EXPAND_AS_DEFINED. Do you have any idea what I do wrong? (Doxygen version 1.5.1)

Regards,

Petr

Would you like to post a relpy?


This post is a reply to:
By Peter Dimov (8. August 2007, 18:29:57)
Re: Compiling without warnings issues
 (3)
Hi Petr, > warning: switch missing default case| I had that one too somewhere last time I fixed warnings. I know that I insisted on not writing the default: because otherwise we (more...)

Follow-ups:
By Peter Dimov (8. August 2007, 22:11:57)
Re: Compiling without warnings issues
 (1)
Hi Petr, I'm totally mystified at first because adding the following to one of the test cpp files worked: class TestDummy { public: VALUE_OBJECT (TestDummy) }; class TestDummy2 { REFERENCE_OBJECT (TestDummy2) public: }; class TestDummy3 { STATIC_HELPER (TestDummy3) public: }; Then I though that because Doxygen parses (more...)