Hi Richard,
cool, didn't now about "ENABLE_PREPROCESSING" yet.
but it's a bit more complicated (for me;), as ENABLE_PREPROCESSING is
already active by default.
and there is a #define EXPORT <nothing> (which originally was blocked by
//\cond IGNORE_DOXYGEN)
when removing IGNORE_DOXYGEN, then that EXPORT shows up in a list of
defines,
and stays in the docs (now in blue) with link to the doc of the empty
definition of EXPORT...
BUT with
PREDEFINED = EXPORT
EXPAND_ONLY_PREDEF = YES
in the config file (exactly as you mentioned, now that I found it;) and
IGNORE_DOXYGEN it's fine.
thanks a lot for your very quick help!!
Harald
On 7/22/20 2:22 PM, Richard Damon wrote:
On 7/22/20 7:49 AM, Harald.Koenig2 via Doxygen-users wrote:
Hi *,
I'm new to doxygen, using git master branch (cf635ef1) on Ubuntu 18.04
(right now mostly with TeXlive 2018 for compatibility by default, TL
2020 installed to).
the C sources to be documented (not my own code) uses an "EXPORT" define
for some plattforms (e.g. "__declspec(dllexport)" for WIN32):
foo.h:
EXPORT int foo(void);
and of course this "EXPORT" shows up in doxygen output.
question: how to get rid of these "EXPORT"s in doxygen??
right I'm using sed to hack the tex files:
sed -i 's/E\\+X\\+P\\+O\\+RT//g' *.tex
there must be a better way??
thanks,
Harald
Enable preprocessing (maybe predefined only) and put a define in you
config file to map EXPORT to nothing. Maybe even you want to also map
__declspec(x) to nothing too.
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
