I am documenting a library with Doxygen and want to generate man pages that
could ship with it. Doxygen is generating 2 very odd, and empty except for some
man page boilerplate, man pages
_path_to_my_project_include_.3
_path_to_my_project_lib_.3
The files correspond to the Doxygen's INPUT
/path/to/my/project/include
/path/to/my/project/lib
include is given in INPUT. lib is the parent of some .c source files given in
INPUT. include & lib are in the directory containing the doxyConfig file which
is also the current directory when I run Doxygen.
With Doxygen 1.8.9 the files contained lists respectively of the .h files in
the include directory and the .c files in the lib directory.
How can I stop Doxygen from generating these useless files? Even if they had
any content, the man page names being specific to my environment make them
useless.
Also asked on stackoverflow
<http://stackoverflow.com/questions/43677909/how-can-i-stop-doxygen-creating-a-path-to-my-proj-lib-3-man-page>.
Regards
-Mark
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
