Geoff Worboys wrote:
> I'm having some very odd problems with EXPAND_AS_DEFINED
For the record of this list I thought I should add a follow up.
Dimitri discovered a problem, specific to Windows, associated
with INCLUDE_PATH (part of the preprocessing settings in
doxygen) that can cause doxygen to
Dimitri van Heesch wrote:
> Sounds like an issue that needs to be fixed. If someone else
> has a self-contained example showing this issue, please
> file a bug report here:
> https://bugzilla.gnome.org/enter_bug.cgi?product=doxygen
> and attach the example.
Yippee! I finally did it:
https://b
siscomputing.com.au]
> Sent: Wednesday, June 05, 2013 5:58 AM
> To: doxygen-users@lists.sourceforge.net
> Subject: [Doxygen-users] Strange problems with EXPAND_AS_DEFINED
>
> Hi all,
>
> Regarding doxygen v1.8.4 on Windows 7 (64bit)
>
> I'm having some very odd p
5:58 AM
To: doxygen-users@lists.sourceforge.net
Subject: [Doxygen-users] Strange problems with EXPAND_AS_DEFINED
Hi all,
Regarding doxygen v1.8.4 on Windows 7 (64bit)
I'm having some very odd problems with EXPAND_AS_DEFINED
Basically it comes down to not expanding macros that are
defined i
Hi all,
Regarding doxygen v1.8.4 on Windows 7 (64bit)
I'm having some very odd problems with EXPAND_AS_DEFINED
Basically it comes down to not expanding macros that are
defined inside header files in the project. If I move the
definition inside the source file it works.
BUT it's not that simpl
