As I reported on the list last week, @cond/@endcond did work to conditionalize
#defines in Doxygen 1.8.2, but sinc 1.8.3 (or maybe since 1.8.3.1), Doxygen
seems to be processing #defines even in @cond blocks.
As far as I can tell, @cond still works fine for everything else.
Regards,
Ne
The @cond and /endcond commands do not always work. The project that I am
working on has examples of where they do work and where they don't work. There
does not seem to be any pattern to this. Below is an example of where they do
not work, on a very short and simple file. I have tried ALL o
[cid:image002.png@01CE02F8.6D56E7C0]
image001.emz
Description: image001.emz
<>
oledata.mso
Description: oledata.mso
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
a
Dude (nice nickname)
One possible solution is to place conditional guards around your prototypes
in the files where you don't want them included:
/* @cond ONLY_INCLUDE_THE_FOLLOWING_IF_I_DEFINE_THIS_NAME */
Function prototypes go here
/* @endcond */
Place these two comments around what you don
So I have a C program that is split into multiple objects. My makefile looks
like this:
*all: fadingsim.o jakesimulator.o dspmath_fp.o
g++ fadingsim.o jakesimulator.o dspmath_fp.o -o fadingsim
#Main#
fadingsim.o: fadingsim.c constants.h
g++ -c -Wall fadingsim.c
jakesimulator.o:
