Jonas, Ignore what I said before as these do need to be separate targets. It appears the new targets are running doxygen. This isn’t something we typically do as a post commit hook since it takes awhile. I’ll need to do this via the doxygen nightly script. Any concerns?
-Tanya > On Apr 23, 2019, at 11:45 AM, Tanya Lattner <tanyalatt...@llvm.org> wrote: > > Anytime new targets are added, the script has to be modified. Is there a way > you can put them all under a top level html target? Or is there a reason not > to? > > -Tanya > >> On Apr 19, 2019, at 12:17 PM, Jonas Devlieghere <jo...@devlieghere.com >> <mailto:jo...@devlieghere.com>> wrote: >> >> Hey Tanya, >> >> Thanks again for migrating the LLDB website so it is generated with Sphinx! >> >> I made a change yesterday that hasn't been propagated yet. It looks like it >> might have something to do with >> http://lists.llvm.org/pipermail/www-scripts/2019-April/007524.html >> <http://lists.llvm.org/pipermail/www-scripts/2019-April/007524.html>. >> >> Also, as the result of this change the following two links are broken: >> >> https://lldb.llvm.org/cpp_reference/ <https://lldb.llvm.org/cpp_reference/> >> https://lldb.llvm.org/python_reference/ >> <https://lldb.llvm.org/python_reference/> >> >> Could we make the script generate those two folders as well? The >> corresponding CMake target are lldb-cpp-doc and lldb-python-doc. >> >> Thank you,Or >> Jonas >> >> PS: I've included lldb-dev in CC so everyone knows we're working on the >> missing documentation. >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
