<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 14, 2016, at 6:44 AM, Tamas Berghammer via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi All,<div class=""><br class=""></div><div class="">The current LLDB API reference documentation available at <a href="http://lldb.llvm.org/python_reference/index.html" class="">http://lldb.llvm.org/python_reference/</a> and at <a href="http://lldb.llvm.org/cpp_reference/html/" class="">http://lldb.llvm.org/cpp_reference/html/</a> but it haven't been updated since July 2013.</div><div class=""><br class=""></div><div class="">I am planning to regenerate it next week using "ninja lldb-cpp-doc lldb-python-doc" (from a Linux machine using epydoc 3.0.1 and doxygen 1.8.6) to get them up to date. Is there any objection against it?</div><div class=""><br class=""></div><div class="">Additionally, in the future it would be great if we can keep the generated doc more up to date after additions to the SB API so users of LLDB can rely it.</div></div></div></blockquote><div><br class=""></div></div>There is a bot continuously updating <a href="http://llvm.org/docs/" class="">http://llvm.org/docs/</a> ; ideally we should be able to hook the other LLVM sub-projects there.<div class=""><br class=""></div><div class="">— </div><div class="">Mehdi</div></body></html>