Currently our online C++ API documentation pages for graphics are always generated using OpenGL API. These pages are automatically generated by our Travis-CI job, so that's why it is using OpenGL. On AppVeyor CI side, we do have the possibility to upload the API documentation pages that are generated using DX11 graphics API. However, this is not an ideal solution because we would then have two almost identical documents on our GitHub Pages which only differ in the backend graphics API class reference. So, I wonder are there any Doxygen special commands that we can use to solve this problem by generating all the class references in a single set of documentation and some how has separate groups for each graphics API? Anybody knows? At the moment we do not use "module" groupings, but I am also not sure it can be used for this purpose.
Statistics: Posted Posted by weitjong — 01 Jun 2016, 11:44