2

I have a C++ package that allows for different behavior if the user defines different pre-processor constants. For example, a user can use /D ALLOW_WIDE_CHAR in the makefile to change the behavior to support wide characters.

I would like to document these options with Doxygen, but Doxygen complains because there is no actual #define in the code. It is up to the user to do that.

Adding the definition to the PREDEFINED list in the configuration file doesn't help.

Suggestions?

1 Answer 1

2

One option I found is to create an extra source file, say Doxygen.h, that is not compiled, but is added to the Doxygen file list. This file can use #define to define those pre-processor constants. It seems like there should be a better solution, though.

Sign up to request clarification or add additional context in comments.

1 Comment

This is the best option I've seen so far, but definitely still not ideal :(

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.