From: Matt L. <mat...@ki...> - 2010-03-01 20:03:26
|
VXL Developers, I'm in the process of restoring nightly builds of the Kitware hosted VXL documentation (book and doxygen). I've switched to the CMake based documentation build that Miguel implemented a while back. I really appreciate Miguel's effort to migrate the documentation build to CMake. Building the docs is so much easier now. A first build is online at the same addresses currently linked from the VXL homepage. For example, http://public.kitware.com/vxl/doc/development/index.html I'm still testing the script scheduling to make sure this runs every day. It should be back on a nightly update schedule soon. I've run into a few issues related to the "algo" libraries. Doxygen seems to create extra library entries for vnl_algo, vil_algo, and vgl_algo under core-L2. All of these are named "algo" on the index page. As with older builds, all the algo code is also available under the base library documentation. For example, the vnl package documents vnl, vnl/algo, vnl/io, and vnl/xio. The new "algo" package entries seem to contain a subset of the base library documentation (i.e. lists files in the algo directory but no "classes" link is generated). Also, I've noticed that the base libraries seem to incorrectly use the introduction_doxy.txt from the algo directory when one is present. For example see http://public.kitware.com/vxl/doc/development/core/vnl/html/index.html This error also occurs with the Brown and Manchester builds. Should the "doxygen_add_library" commands be removed from v*l/algo/CMakeList.txt? Should the v*l/algo/introduction_doxy.txt be merged into v*l/introduction_doxy.txt? Can anyone suggest an alternative solution? Thanks, Matt |