----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119678/#review64940 -----------------------------------------------------------
Thanks for working on this! I agree that the generated documentation can be useful (even though some of the generated HTML pages are quite overwhelming). I'm not extremely familiar with Doxygen, but since this might be interesting also for other projects/repositories, I'm wondering if there is a way to achieve that without adding a huge new file to every single repository? - Frank Reininghaus On Aug. 9, 2014, 12:43 a.m., Mathieu Tarral wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/119678/ > ----------------------------------------------------------- > > (Updated Aug. 9, 2014, 12:43 a.m.) > > > Review request for KDE Base Apps. > > > Repository: kde-baseapps > > > Description > ------- > > add a target named <project>_doc for each project in the tree, to generate > developer documention by extracting code structure, and creating useful call > graphs. It's very useful to new contributors, so they can find their way into > the source tree by exploring files and structures into their favorite browser. > > > Diffs > ----- > > CMakeLists.txt b06ba01fff7cee445fcc0b896cef041bd4c34fc8 > cmake/in/Doxyfile.in.cmake PRE-CREATION > cmake/modules/doxygen.cmake PRE-CREATION > > Diff: https://git.reviewboard.kde.org/r/119678/diff/ > > > Testing > ------- > > mkdir _build > cd _build > cmake .. -DCMAKE_INSTALL_PREFIX=../_install > make dolphin_doc > make kdialog_doc > etc ... > > > Thanks, > > Mathieu Tarral > >
