By adding *.h.in and *cc.in to the FILE_PATTERNS, I can get these almost-C
files documented usefully. (They are subject to CMake configure_file, after
which they are placed in the build tree. I don't want to treat the build tree
as a Doxygen input location, because it's not in the same place, even with
respect to current directory, on each developer's machine. Even more true if
the developer is trying to document just a subdirectory of the main source
tree.)
However, in EXTENSION_MAPPINGS, h.in=C does not seem to work. The file is
included, but not analyzed as C source. I have to use in=C. This becomes a
problem if I ever want to have Doxygen work on py.in files, which have to be
mapped to the Python generator.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
