Le jeu. 21 févr. 2019 à 06:19, Timothy Wrona a
écrit :
>
> Either way having it as an "index.html" file somewhere on the hard-disk is
> not very intuitive. It would make much more sense for it to be on a web
> server where you can access it with a sensible URL.
>
Unless it's linked from some fro
On 21/02/2019 14:18, Timothy Wrona wrote:
Perhaps there is a standard location to "install" the documentation when
running the install command for a project?
This collection builds and installs the documentation into a standard
location, as well as reporting undocumented code. Feel free to co
Hi Timothy,
This is not something I'm very familiar with, but maybe I
can still add a little to the discussion by answering both
of your messages together.
On 21/2/2019 10:18 PM, Timothy Wrona wrote:
Perhaps there is a standard location to "install" the
documentation when running the insta
Perhaps there is a standard location to "install" the documentation when
running the install command for a project?
Either way having it as an "index.html" file somewhere on the hard-disk is
not very intuitive. It would make much more sense for it to be on a web
server where you can access it with
On 2019-02-20 17:52-0500 Timothy Wrona wrote:
I have worked on multiple C++ libraries that are built with CMake and run
Doxygen to generate HTML documentation. In every one of these libraries,
the documentation get's built into an "html" folder in the CMake "build"
directory and never gets looke
I have worked on multiple C++ libraries that are built with CMake and run
Doxygen to generate HTML documentation. In every one of these libraries,
the documentation get's built into an "html" folder in the CMake "build"
directory and never gets looked at by anyone.
*Because let's be honest, most p