subject:"\[lldb\-dev\] LLDB Website"

Re: [lldb-dev] LLDB Website is not being updated

2020-03-02 Thread Jonas Devlieghere via lldb-dev

I removed the version number from the home page.

To github.com:llvm/llvm-project.git
   adc69729ec8..c77fc00eec0  master -> master

I'm not sure we should have the banner because (1) the documentation
doesn't change as much as llvm/clang and (2) we don't archive the old
documentation so there's nothing to link to.

On Mon, Mar 2, 2020 at 1:47 PM Adrian Prantl  wrote:

> Ah, that's great! We should probably just don't print a version on this
> variant and/or add a box like the one at the top of http://llvm.org/docs/.
>
> thanks,
> adrian
>
> On Mar 2, 2020, at 1:43 PM, Jonas Devlieghere 
> wrote:
>
> Hey Adrian,
>
> The version is hard-coded in lldb/docs/conf.py, we just need to update it
> there. As far as I know the website is being updated nightly.
>
> Cheers,
> Jonas
>
> On Mon, Mar 2, 2020 at 1:41 PM Adrian Prantl  wrote:
>
>> Hello Tanya,
>>
>> I just looked at the LLDB website and it still displays the out-of-date
>> "version 8" page. Did you get a chance to investigate this in the mean time?
>>
>> thanks,
>> adrian
>>
>> > On Nov 24, 2019, at 8:30 AM, Tanya Lattner 
>> wrote:
>> >
>> > I’ll have to check the status of moving the scripts over and what is
>> going on. But yes, this is all related to moving to GitHub and modifying
>> scripts that used to be either on a post-commit hook or nightly cron.
>> >
>> > -Tanya
>> >
>> >> On Nov 21, 2019, at 3:04 PM, Jonas Devlieghere 
>> wrote:
>> >>
>> >> I see a bunch of eros here:
>> >> http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html
>> >>
>> >> Is this possibly related to the Github/monorepo transition?
>> >>
>> >> -- Jonas
>> >>
>> >> On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
>> >>  wrote:
>> >>>
>> >>> Hello Tanya,
>> >>>
>> >>> it looks like the cron job that is supposed to be updating the LLDB
>> website isn't running or is otherwise blocked at the moment. You can see on
>> https://lldb.llvm.org that it says "Welcome to the LLDB version 8
>> documentation!". We also recently removed the "Why a New Debugger?"
>> headline and that change isn't showing up either.
>> >>>
>> >>> Would you mind taking a look?
>> >>>
>> >>> thanks for your help,
>> >>> Adrian
>> >>> ___
>> >>> lldb-dev mailing list
>> >>> lldb-dev@lists.llvm.org
>> >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>> >
>>
>>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website is not being updated

2020-03-02 Thread Adrian Prantl via lldb-dev

Ah, that's great! We should probably just don't print a version on this variant 
and/or add a box like the one at the top of http://llvm.org/docs/ 
.

thanks,
adrian

> On Mar 2, 2020, at 1:43 PM, Jonas Devlieghere  wrote:
> 
> Hey Adrian,
> 
> The version is hard-coded in lldb/docs/conf.py, we just need to update it 
> there. As far as I know the website is being updated nightly.
> 
> Cheers,
> Jonas
> 
> On Mon, Mar 2, 2020 at 1:41 PM Adrian Prantl  > wrote:
> Hello Tanya,
> 
> I just looked at the LLDB website and it still displays the out-of-date 
> "version 8" page. Did you get a chance to investigate this in the mean time?
> 
> thanks,
> adrian
> 
> > On Nov 24, 2019, at 8:30 AM, Tanya Lattner  > > wrote:
> > 
> > I’ll have to check the status of moving the scripts over and what is going 
> > on. But yes, this is all related to moving to GitHub and modifying scripts 
> > that used to be either on a post-commit hook or nightly cron.
> > 
> > -Tanya
> > 
> >> On Nov 21, 2019, at 3:04 PM, Jonas Devlieghere  >> > wrote:
> >> 
> >> I see a bunch of eros here:
> >> http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html 
> >> 
> >> 
> >> Is this possibly related to the Github/monorepo transition?
> >> 
> >> -- Jonas
> >> 
> >> On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
> >> mailto:lldb-dev@lists.llvm.org>> wrote:
> >>> 
> >>> Hello Tanya,
> >>> 
> >>> it looks like the cron job that is supposed to be updating the LLDB 
> >>> website isn't running or is otherwise blocked at the moment. You can see 
> >>> on https://lldb.llvm.org  that it says "Welcome 
> >>> to the LLDB version 8 documentation!". We also recently removed the "Why 
> >>> a New Debugger?" headline and that change isn't showing up either.
> >>> 
> >>> Would you mind taking a look?
> >>> 
> >>> thanks for your help,
> >>> Adrian
> >>> ___
> >>> lldb-dev mailing list
> >>> lldb-dev@lists.llvm.org 
> >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev 
> >>> 
> > 
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website is not being updated

2020-03-02 Thread Jonas Devlieghere via lldb-dev

Hey Adrian,

The version is hard-coded in lldb/docs/conf.py, we just need to update it
there. As far as I know the website is being updated nightly.

Cheers,
Jonas

On Mon, Mar 2, 2020 at 1:41 PM Adrian Prantl  wrote:

> Hello Tanya,
>
> I just looked at the LLDB website and it still displays the out-of-date
> "version 8" page. Did you get a chance to investigate this in the mean time?
>
> thanks,
> adrian
>
> > On Nov 24, 2019, at 8:30 AM, Tanya Lattner 
> wrote:
> >
> > I’ll have to check the status of moving the scripts over and what is
> going on. But yes, this is all related to moving to GitHub and modifying
> scripts that used to be either on a post-commit hook or nightly cron.
> >
> > -Tanya
> >
> >> On Nov 21, 2019, at 3:04 PM, Jonas Devlieghere 
> wrote:
> >>
> >> I see a bunch of eros here:
> >> http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html
> >>
> >> Is this possibly related to the Github/monorepo transition?
> >>
> >> -- Jonas
> >>
> >> On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
> >>  wrote:
> >>>
> >>> Hello Tanya,
> >>>
> >>> it looks like the cron job that is supposed to be updating the LLDB
> website isn't running or is otherwise blocked at the moment. You can see on
> https://lldb.llvm.org that it says "Welcome to the LLDB version 8
> documentation!". We also recently removed the "Why a New Debugger?"
> headline and that change isn't showing up either.
> >>>
> >>> Would you mind taking a look?
> >>>
> >>> thanks for your help,
> >>> Adrian
> >>> ___
> >>> lldb-dev mailing list
> >>> lldb-dev@lists.llvm.org
> >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
> >
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website is not being updated

2020-03-02 Thread Adrian Prantl via lldb-dev

Hello Tanya,

I just looked at the LLDB website and it still displays the out-of-date 
"version 8" page. Did you get a chance to investigate this in the mean time?

thanks,
adrian

> On Nov 24, 2019, at 8:30 AM, Tanya Lattner  wrote:
> 
> I’ll have to check the status of moving the scripts over and what is going 
> on. But yes, this is all related to moving to GitHub and modifying scripts 
> that used to be either on a post-commit hook or nightly cron.
> 
> -Tanya
> 
>> On Nov 21, 2019, at 3:04 PM, Jonas Devlieghere  wrote:
>> 
>> I see a bunch of eros here:
>> http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html
>> 
>> Is this possibly related to the Github/monorepo transition?
>> 
>> -- Jonas
>> 
>> On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
>>  wrote:
>>> 
>>> Hello Tanya,
>>> 
>>> it looks like the cron job that is supposed to be updating the LLDB website 
>>> isn't running or is otherwise blocked at the moment. You can see on 
>>> https://lldb.llvm.org that it says "Welcome to the LLDB version 8 
>>> documentation!". We also recently removed the "Why a New Debugger?" 
>>> headline and that change isn't showing up either.
>>> 
>>> Would you mind taking a look?
>>> 
>>> thanks for your help,
>>> Adrian
>>> ___
>>> lldb-dev mailing list
>>> lldb-dev@lists.llvm.org
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website is not being updated

2019-11-24 Thread Tanya Lattner via lldb-dev

I’ll have to check the status of moving the scripts over and what is going on. 
But yes, this is all related to moving to GitHub and modifying scripts that 
used to be either on a post-commit hook or nightly cron.

-Tanya

> On Nov 21, 2019, at 3:04 PM, Jonas Devlieghere  wrote:
> 
> I see a bunch of eros here:
> http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html
> 
> Is this possibly related to the Github/monorepo transition?
> 
> -- Jonas
> 
> On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
>  wrote:
>> 
>> Hello Tanya,
>> 
>> it looks like the cron job that is supposed to be updating the LLDB website 
>> isn't running or is otherwise blocked at the moment. You can see on 
>> https://lldb.llvm.org that it says "Welcome to the LLDB version 8 
>> documentation!". We also recently removed the "Why a New Debugger?" headline 
>> and that change isn't showing up either.
>> 
>> Would you mind taking a look?
>> 
>> thanks for your help,
>> Adrian
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website is not being updated

2019-11-21 Thread Jonas Devlieghere via lldb-dev

I see a bunch of eros here:
http://lists.llvm.org/pipermail/www-scripts/2019-November/thread.html

Is this possibly related to the Github/monorepo transition?

-- Jonas

On Thu, Nov 21, 2019 at 10:52 AM Adrian Prantl via lldb-dev
 wrote:
>
> Hello Tanya,
>
> it looks like the cron job that is supposed to be updating the LLDB website 
> isn't running or is otherwise blocked at the moment. You can see on 
> https://lldb.llvm.org that it says "Welcome to the LLDB version 8 
> documentation!". We also recently removed the "Why a New Debugger?" headline 
> and that change isn't showing up either.
>
> Would you mind taking a look?
>
> thanks for your help,
> Adrian
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] LLDB Website is not being updated

2019-11-21 Thread Adrian Prantl via lldb-dev

Hello Tanya,

it looks like the cron job that is supposed to be updating the LLDB website 
isn't running or is otherwise blocked at the moment. You can see on 
https://lldb.llvm.org that it says "Welcome to the LLDB version 8 
documentation!". We also recently removed the "Why a New Debugger?" headline 
and that change isn't showing up either.

Would you mind taking a look?

thanks for your help,
Adrian
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

2019-05-07 Thread Jonas Devlieghere via lldb-dev

hanges before to prevent any
>>>> issue.
>>>>
>>>> -Tanya
>>>>
>>>> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere 
>>>> wrote:
>>>>
>>>> I've merged the aforementioned patch.
>>>>
>>>> Tanya, can you give generating the python docs another shot?
>>>>
>>>> Thanks,
>>>> Jonas
>>>>
>>>> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere <
>>>> jo...@devlieghere.com> wrote:
>>>>
>>>>> I've put up a patch to make it possible to generate the python
>>>>> reference without building lldb at all:
>>>>> https://reviews.llvm.org/D61216
>>>>>
>>>>> PS: The website isn't updating anymore, is that because of the python
>>>>> reference generation?
>>>>>
>>>>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward 
>>>>> wrote:
>>>>>
>>>>>> That's the issue - lldb-python-doc depends on liblldb. From
>>>>>> docs/CMakeLists.txt:
>>>>>>
>>>>>> if(EPYDOC_EXECUTABLE)
>>>>>>   find_program(DOT_EXECUTABLE dot)
>>>>>> if(DOT_EXECUTABLE)
>>>>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath
>>>>>> ${DOT_EXECUTABLE})
>>>>>> endif()
>>>>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>>>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>>>>> #set(ENV{PYTHONPATH}
>>>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>>>>> add_custom_target(lldb-python-doc
>>>>>>   ${EPYDOC_EXECUTABLE}
>>>>>>   --html
>>>>>>   lldb
>>>>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>>>>   --name "LLDB python API"
>>>>>>   --url "http://lldb.llvm.org;
>>>>>>   ${EPYDOC_OPTIONS}
>>>>>>   DEPENDS swig_wrapper liblldb
>>>>>>   WORKING_DIRECTORY
>>>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>>>>   COMMENT "Generating LLDB Python API reference with epydoc"
>>>>>> VERBATIM
>>>>>> )
>>>>>> endif(EPYDOC_EXECUTABLE)
>>>>>>
>>>>>>
>>>>>> > -Original Message-
>>>>>> > From: lldb-dev  On Behalf Of
>>>>>> Pavel Labath
>>>>>> > via lldb-dev
>>>>>> > Sent: Wednesday, April 24, 2019 1:16 AM
>>>>>> > To: Jonas Devlieghere ; Tanya Lattner
>>>>>> > 
>>>>>> > Cc: LLDB 
>>>>>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>>>>>> >
>>>>>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>>>>>> > >
>>>>>> > >
>>>>>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>>>>>> > > mailto:jo...@devlieghere.com>> wrote:
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner <
>>>>>> tanyalatt...@llvm.org
>>>>>> > > <mailto:tanyalatt...@llvm.org>> wrote:
>>>>>> > >
>>>>>> > >
>>>>>> > >
>>>>>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>>>>>> > >> mailto:jo...@devlieghere.com>>
>>>>>> wrote:
>>>>>> > >>
>>>>>> > >>
>>>>>> > >>
>>>>>> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
>>>>>> > >> mailto:tanyalatt...@llvm.org>>
>>>>>> wrote:
>>>>>> > >>
>>>>>> > >>
>>>>>> > >>
>>>>>> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
>>>>>> > >>> >>>>> jo...@devlieghere.com>>
>>>>>> > wrote:
>>>>>> > >

Re: [lldb-dev] LLDB Website

2019-05-07 Thread Tanya Lattner via lldb-dev

On Wed, May 1, 2019 at 10:40 PM Tanya Lattner >>> <mailto:tanyalatt...@llvm.org>> wrote:
>>>> I will give this a shot. I did remove the changes before to prevent any 
>>>> issue.
>>>> 
>>>> -Tanya
>>>> 
>>>>> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere >>>> <mailto:jo...@devlieghere.com>> wrote:
>>>>> 
>>>>> I've merged the aforementioned patch. 
>>>>> 
>>>>> Tanya, can you give generating the python docs another shot?
>>>>> 
>>>>> Thanks,
>>>>> Jonas
>>>>> 
>>>>> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere >>>> <mailto:jo...@devlieghere.com>> wrote:
>>>>> I've put up a patch to make it possible to generate the python reference 
>>>>> without building lldb at all: https://reviews.llvm.org/D61216 
>>>>> <https://reviews.llvm.org/D61216>
>>>>> 
>>>>> PS: The website isn't updating anymore, is that because of the python 
>>>>> reference generation?
>>>>> 
>>>>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward >>>> <mailto:tedw...@quicinc.com>> wrote:
>>>>> That's the issue - lldb-python-doc depends on liblldb. From 
>>>>> docs/CMakeLists.txt:
>>>>> 
>>>>> if(EPYDOC_EXECUTABLE)
>>>>>   find_program(DOT_EXECUTABLE dot)
>>>>> if(DOT_EXECUTABLE)
>>>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
>>>>> ${DOT_EXECUTABLE})
>>>>> endif()
>>>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>>>> #set(ENV{PYTHONPATH} 
>>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>>>> add_custom_target(lldb-python-doc
>>>>>   ${EPYDOC_EXECUTABLE}
>>>>>   --html
>>>>>   lldb
>>>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>>>   --name "LLDB python API"
>>>>>   --url "http://lldb.llvm.org <http://lldb.llvm.org/>"
>>>>>   ${EPYDOC_OPTIONS}
>>>>>   DEPENDS swig_wrapper liblldb
>>>>>   WORKING_DIRECTORY 
>>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>>>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
>>>>> )
>>>>> endif(EPYDOC_EXECUTABLE)
>>>>> 
>>>>> 
>>>>> > -Original Message-
>>>>> > From: lldb-dev >>>> > <mailto:lldb-dev-boun...@lists.llvm.org>> On Behalf Of Pavel Labath
>>>>> > via lldb-dev
>>>>> > Sent: Wednesday, April 24, 2019 1:16 AM
>>>>> > To: Jonas Devlieghere >>>> > <mailto:jo...@devlieghere.com>>; Tanya Lattner
>>>>> > mailto:tanyalatt...@llvm.org>>
>>>>> > Cc: LLDB mailto:lldb-dev@lists.llvm.org>>
>>>>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>>>>> > 
>>>>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>>>>> > >
>>>>> > >
>>>>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>>>>> > > mailto:jo...@devlieghere.com> 
>>>>> > > <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>> wrote:
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner 
>>>>> > > mailto:tanyalatt...@llvm.org>
>>>>> > > <mailto:tanyalatt...@llvm.org <mailto:tanyalatt...@llvm.org>>> 
>>>>> > > wrote:
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>>>>> > >> mailto:jo...@devlieghere.com> 
>>>>> > >> <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>> wrote:
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> On Tue, Apr 23, 2019

Re: [lldb-dev] LLDB Website

2019-05-07 Thread Jonas Devlieghere via lldb-dev

>> wrote:
>>>>
>>>>> That's the issue - lldb-python-doc depends on liblldb. From
>>>>> docs/CMakeLists.txt:
>>>>>
>>>>> if(EPYDOC_EXECUTABLE)
>>>>>   find_program(DOT_EXECUTABLE dot)
>>>>> if(DOT_EXECUTABLE)
>>>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath
>>>>> ${DOT_EXECUTABLE})
>>>>> endif()
>>>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>>>> #set(ENV{PYTHONPATH}
>>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>>>> add_custom_target(lldb-python-doc
>>>>>   ${EPYDOC_EXECUTABLE}
>>>>>   --html
>>>>>   lldb
>>>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>>>   --name "LLDB python API"
>>>>>   --url "http://lldb.llvm.org;
>>>>>   ${EPYDOC_OPTIONS}
>>>>>   DEPENDS swig_wrapper liblldb
>>>>>   WORKING_DIRECTORY
>>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>>>   COMMENT "Generating LLDB Python API reference with epydoc"
>>>>> VERBATIM
>>>>> )
>>>>> endif(EPYDOC_EXECUTABLE)
>>>>>
>>>>>
>>>>> > -Original Message-
>>>>> > From: lldb-dev  On Behalf Of Pavel
>>>>> Labath
>>>>> > via lldb-dev
>>>>> > Sent: Wednesday, April 24, 2019 1:16 AM
>>>>> > To: Jonas Devlieghere ; Tanya Lattner
>>>>> > 
>>>>> > Cc: LLDB 
>>>>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>>>>> >
>>>>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>>>>> > >
>>>>> > >
>>>>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>>>>> > > mailto:jo...@devlieghere.com>> wrote:
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner <
>>>>> tanyalatt...@llvm.org
>>>>> > > <mailto:tanyalatt...@llvm.org>> wrote:
>>>>> > >
>>>>> > >
>>>>> > >
>>>>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>>>>> > >> mailto:jo...@devlieghere.com>>
>>>>> wrote:
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
>>>>> > >> mailto:tanyalatt...@llvm.org>>
>>>>> wrote:
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
>>>>> > >>> mailto:jo...@devlieghere.com
>>>>> >>
>>>>> > wrote:
>>>>> > >>>
>>>>> > >>> Hey Tanya,
>>>>> > >>>
>>>>> > >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
>>>>> > >>> mailto:tanyalatt...@llvm.org>>
>>>>> wrote:
>>>>> > >>>
>>>>> > >>> 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?
>>>>> > >>>
>>>>> > >>> That sounds perfect. Can we still do the regular
>>>>> website
>>>>> > >>> post commit?
>>&

Re: [lldb-dev] LLDB Website

2019-05-07 Thread Tanya Lattner via lldb-dev

BLE)
>>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
>>>> ${DOT_EXECUTABLE})
>>>> endif()
>>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>>> #set(ENV{PYTHONPATH} 
>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>>> add_custom_target(lldb-python-doc
>>>>   ${EPYDOC_EXECUTABLE}
>>>>   --html
>>>>   lldb
>>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>>   --name "LLDB python API"
>>>>   --url "http://lldb.llvm.org <http://lldb.llvm.org/>"
>>>>   ${EPYDOC_OPTIONS}
>>>>   DEPENDS swig_wrapper liblldb
>>>>   WORKING_DIRECTORY 
>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
>>>> )
>>>> endif(EPYDOC_EXECUTABLE)
>>>> 
>>>> 
>>>> > -Original Message-
>>>> > From: lldb-dev >>> > <mailto:lldb-dev-boun...@lists.llvm.org>> On Behalf Of Pavel Labath
>>>> > via lldb-dev
>>>> > Sent: Wednesday, April 24, 2019 1:16 AM
>>>> > To: Jonas Devlieghere >>> > <mailto:jo...@devlieghere.com>>; Tanya Lattner
>>>> > mailto:tanyalatt...@llvm.org>>
>>>> > Cc: LLDB mailto:lldb-dev@lists.llvm.org>>
>>>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>>>> > 
>>>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>>>> > >
>>>> > >
>>>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>>>> > > mailto:jo...@devlieghere.com> 
>>>> > > <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>> wrote:
>>>> > >
>>>> > >
>>>> > >
>>>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner 
>>>> > > mailto:tanyalatt...@llvm.org>
>>>> > > <mailto:tanyalatt...@llvm.org <mailto:tanyalatt...@llvm.org>>> 
>>>> > > wrote:
>>>> > >
>>>> > >
>>>> > >
>>>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>>>> > >> mailto:jo...@devlieghere.com> 
>>>> > >> <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>> wrote:
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
>>>> > >> mailto:tanyalatt...@llvm.org> 
>>>> > >> <mailto:tanyalatt...@llvm.org <mailto:tanyalatt...@llvm.org>>> wrote:
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
>>>> > >>> mailto:jo...@devlieghere.com> 
>>>> > >>> <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>>
>>>> > wrote:
>>>> > >>>
>>>> > >>> Hey Tanya,
>>>> > >>>
>>>> > >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
>>>> > >>> mailto:tanyalatt...@llvm.org> 
>>>> > >>> <mailto:tanyalatt...@llvm.org <mailto:tanyalatt...@llvm.org>>> wrote:
>>>> > >>>
>>>> > >>> 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?
>>>> > >>>
>>>> > >>> That sounds perfect. Can we still do the regular website
>>&g

Re: [lldb-dev] LLDB Website

2019-05-07 Thread Jonas Devlieghere via lldb-dev

Hey Tanya,

That's great. I see the Python documentation is online now!

Unfortunately it appears that the Sphinx part still isn't updating. I
pushed a bunch of changes last week and none have made it to the homepage
yet. I checked the www-scripts mailing list but I don't see any failures
for LLDB. Do you know what's up here?

Thanks,
Jonas

On Tue, May 7, 2019 at 12:19 AM Tanya Lattner  wrote:

> Ignore this. svn wasn’t actually updating the src tree. It works! I just
> need doxygen script to finish and it will be confirmed tonight.
>
>
> -Tanya
>
> On May 6, 2019, at 11:55 PM, Tanya Lattner  wrote:
>
> I’m not sure it is working. To clarify, nothing in LLVM should be compiled
> to build the python docs correct?
>
> So I shouldn’t see this?
> *Scanning dependencies of target liblldb_exports*
> [  0%] *Creating export file for liblldb*
> [  0%] Built target liblldb_exports
> *Scanning dependencies of target LLVMDemangle*
> [  0%] Building CXX object
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
> [  0%] Building CXX object
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o
> [  0%] Building CXX object
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o
> [  0%] Building CXX object
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
> [  0%] *Linking CXX static library ../libLLVMDemangle.a*
> [  0%] Built target LLVMDemangle
> *Scanning dependencies of target LLVMSupport*
> [  0%] Building CXX object
> lib/Support/CMakeFiles/LLVMSupport.dir/AArch64TargetParser.cpp.o
> [  0%] Building CXX object
> lib/Support/CMakeFiles/LLVMSupport.dir/ARMTargetParser.cpp.o
> [  0%] Building CXX object
> lib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o
> [  0%] Building CXX object
> lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o
> [  0%] Building CXX object
> lib/Support/CMakeFiles/LLVMSupport.dir/APInt.cpp.o
>
> Do I need any additional config options?
>
> Thanks,
> Tanya
>
> On May 3, 2019, at 8:58 AM, Jonas Devlieghere 
> wrote:
>
> Hey Tanya,
>
> It appears the website is still stuck. It hasn't picked up my changes from
> earlier this week. Please let me know if there's anything I can do to help.
>
> Thanks,
> Jonas
>
> On Wed, May 1, 2019 at 10:40 PM Tanya Lattner 
> wrote:
>
>> I will give this a shot. I did remove the changes before to prevent any
>> issue.
>>
>> -Tanya
>>
>> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere 
>> wrote:
>>
>> I've merged the aforementioned patch.
>>
>> Tanya, can you give generating the python docs another shot?
>>
>> Thanks,
>> Jonas
>>
>> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere 
>> wrote:
>>
>>> I've put up a patch to make it possible to generate the python reference
>>> without building lldb at all: https://reviews.llvm.org/D61216
>>>
>>> PS: The website isn't updating anymore, is that because of the python
>>> reference generation?
>>>
>>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward 
>>> wrote:
>>>
>>>> That's the issue - lldb-python-doc depends on liblldb. From
>>>> docs/CMakeLists.txt:
>>>>
>>>> if(EPYDOC_EXECUTABLE)
>>>>   find_program(DOT_EXECUTABLE dot)
>>>> if(DOT_EXECUTABLE)
>>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath
>>>> ${DOT_EXECUTABLE})
>>>> endif()
>>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>>> #set(ENV{PYTHONPATH}
>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>>> add_custom_target(lldb-python-doc
>>>>   ${EPYDOC_EXECUTABLE}
>>>>   --html
>>>>   lldb
>>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>>   --name "LLDB python API"
>>>>   --url "http://lldb.llvm.org;
>>>>   ${EPYDOC_OPTIONS}
>>>>   DEPENDS swig_wrapper liblldb
>>>>   WORKING_DIRECTORY
>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>>   COMMENT "Generating LLDB Python API reference with epydoc"
>>>> VERBATIM
>>>> )
>>>> endif(EPYDOC_EXECUTABLE)
>>>>
>>>>
>>>> > -Original Message-
>>>> > From: lldb-dev  On Behalf Of Pavel
>>>> Labath
>>>> > via lldb-dev
>>>>

Re: [lldb-dev] LLDB Website

2019-05-07 Thread Tanya Lattner via lldb-dev

Ignore this. svn wasn’t actually updating the src tree. It works! I just need 
doxygen script to finish and it will be confirmed tonight.


-Tanya

> On May 6, 2019, at 11:55 PM, Tanya Lattner  wrote:
> 
> I’m not sure it is working. To clarify, nothing in LLVM should be compiled to 
> build the python docs correct? 
> 
> So I shouldn’t see this?
> Scanning dependencies of target liblldb_exports
> [  0%] Creating export file for liblldb
> [  0%] Built target liblldb_exports
> Scanning dependencies of target LLVMDemangle
> [  0%] Building CXX object 
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
> [  0%] Building CXX object 
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o
> [  0%] Building CXX object 
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o
> [  0%] Building CXX object 
> lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
> [  0%] Linking CXX static library ../libLLVMDemangle.a
> [  0%] Built target LLVMDemangle
> Scanning dependencies of target LLVMSupport
> [  0%] Building CXX object 
> lib/Support/CMakeFiles/LLVMSupport.dir/AArch64TargetParser.cpp.o
> [  0%] Building CXX object 
> lib/Support/CMakeFiles/LLVMSupport.dir/ARMTargetParser.cpp.o
> [  0%] Building CXX object 
> lib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o
> [  0%] Building CXX object 
> lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o
> [  0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APInt.cpp.o
> 
> Do I need any additional config options?
> 
> Thanks,
> Tanya
> 
>> On May 3, 2019, at 8:58 AM, Jonas Devlieghere > <mailto:jo...@devlieghere.com>> wrote:
>> 
>> Hey Tanya,
>> 
>> It appears the website is still stuck. It hasn't picked up my changes from 
>> earlier this week. Please let me know if there's anything I can do to help.
>> 
>> Thanks,
>> Jonas
>> 
>> On Wed, May 1, 2019 at 10:40 PM Tanya Lattner > <mailto:tanyalatt...@llvm.org>> wrote:
>> I will give this a shot. I did remove the changes before to prevent any 
>> issue.
>> 
>> -Tanya
>> 
>>> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere >> <mailto:jo...@devlieghere.com>> wrote:
>>> 
>>> I've merged the aforementioned patch. 
>>> 
>>> Tanya, can you give generating the python docs another shot?
>>> 
>>> Thanks,
>>> Jonas
>>> 
>>> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere >> <mailto:jo...@devlieghere.com>> wrote:
>>> I've put up a patch to make it possible to generate the python reference 
>>> without building lldb at all: https://reviews.llvm.org/D61216 
>>> <https://reviews.llvm.org/D61216>
>>> 
>>> PS: The website isn't updating anymore, is that because of the python 
>>> reference generation?
>>> 
>>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward >> <mailto:tedw...@quicinc.com>> wrote:
>>> That's the issue - lldb-python-doc depends on liblldb. From 
>>> docs/CMakeLists.txt:
>>> 
>>> if(EPYDOC_EXECUTABLE)
>>>   find_program(DOT_EXECUTABLE dot)
>>> if(DOT_EXECUTABLE)
>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
>>> ${DOT_EXECUTABLE})
>>> endif()
>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>> #set(ENV{PYTHONPATH} 
>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>> add_custom_target(lldb-python-doc
>>>   ${EPYDOC_EXECUTABLE}
>>>   --html
>>>   lldb
>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>   --name "LLDB python API"
>>>   --url "http://lldb.llvm.org <http://lldb.llvm.org/>"
>>>   ${EPYDOC_OPTIONS}
>>>   DEPENDS swig_wrapper liblldb
>>>   WORKING_DIRECTORY 
>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
>>> )
>>> endif(EPYDOC_EXECUTABLE)
>>> 
>>> 
>>> > -Original Message-
>>> > From: lldb-dev >> > <mailto:lldb-dev-boun...@lists.llvm.org>> On Behalf Of Pavel Labath
>>> > via lldb-dev
>>> > Sent: Wednesday, April 24, 2019 1:16 AM
>>> > To: Jonas Devlieghere >> > <mailto:jo...@devlieghere.com>>; Tanya Lattner
>>> > mailto:

Re: [lldb-dev] LLDB Website

2019-05-07 Thread Tanya Lattner via lldb-dev

I’m not sure it is working. To clarify, nothing in LLVM should be compiled to 
build the python docs correct? 

So I shouldn’t see this?
Scanning dependencies of target liblldb_exports
[  0%] Creating export file for liblldb
[  0%] Built target liblldb_exports
Scanning dependencies of target LLVMDemangle
[  0%] Building CXX object 
lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
[  0%] Building CXX object 
lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o
[  0%] Building CXX object 
lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o
[  0%] Building CXX object 
lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
[  0%] Linking CXX static library ../libLLVMDemangle.a
[  0%] Built target LLVMDemangle
Scanning dependencies of target LLVMSupport
[  0%] Building CXX object 
lib/Support/CMakeFiles/LLVMSupport.dir/AArch64TargetParser.cpp.o
[  0%] Building CXX object 
lib/Support/CMakeFiles/LLVMSupport.dir/ARMTargetParser.cpp.o
[  0%] Building CXX object 
lib/Support/CMakeFiles/LLVMSupport.dir/AMDGPUMetadata.cpp.o
[  0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APFloat.cpp.o
[  0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/APInt.cpp.o

Do I need any additional config options?

Thanks,
Tanya

> On May 3, 2019, at 8:58 AM, Jonas Devlieghere  wrote:
> 
> Hey Tanya,
> 
> It appears the website is still stuck. It hasn't picked up my changes from 
> earlier this week. Please let me know if there's anything I can do to help.
> 
> Thanks,
> Jonas
> 
> On Wed, May 1, 2019 at 10:40 PM Tanya Lattner  <mailto:tanyalatt...@llvm.org>> wrote:
> I will give this a shot. I did remove the changes before to prevent any issue.
> 
> -Tanya
> 
>> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere > <mailto:jo...@devlieghere.com>> wrote:
>> 
>> I've merged the aforementioned patch. 
>> 
>> Tanya, can you give generating the python docs another shot?
>> 
>> Thanks,
>> Jonas
>> 
>> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere > <mailto:jo...@devlieghere.com>> wrote:
>> I've put up a patch to make it possible to generate the python reference 
>> without building lldb at all: https://reviews.llvm.org/D61216 
>> <https://reviews.llvm.org/D61216>
>> 
>> PS: The website isn't updating anymore, is that because of the python 
>> reference generation?
>> 
>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward > <mailto:tedw...@quicinc.com>> wrote:
>> That's the issue - lldb-python-doc depends on liblldb. From 
>> docs/CMakeLists.txt:
>> 
>> if(EPYDOC_EXECUTABLE)
>>   find_program(DOT_EXECUTABLE dot)
>> if(DOT_EXECUTABLE)
>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
>> ${DOT_EXECUTABLE})
>> endif()
>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>> file(MAKE_DIRECTORY "${DOC_DIR}")
>> #set(ENV{PYTHONPATH} 
>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>> add_custom_target(lldb-python-doc
>>   ${EPYDOC_EXECUTABLE}
>>   --html
>>   lldb
>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>   --name "LLDB python API"
>>   --url "http://lldb.llvm.org <http://lldb.llvm.org/>"
>>   ${EPYDOC_OPTIONS}
>>   DEPENDS swig_wrapper liblldb
>>   WORKING_DIRECTORY 
>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
>> )
>> endif(EPYDOC_EXECUTABLE)
>> 
>> 
>> > -Original Message-
>> > From: lldb-dev > > <mailto:lldb-dev-boun...@lists.llvm.org>> On Behalf Of Pavel Labath
>> > via lldb-dev
>> > Sent: Wednesday, April 24, 2019 1:16 AM
>> > To: Jonas Devlieghere > > <mailto:jo...@devlieghere.com>>; Tanya Lattner
>> > mailto:tanyalatt...@llvm.org>>
>> > Cc: LLDB mailto:lldb-dev@lists.llvm.org>>
>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>> > 
>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>> > >
>> > >
>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>> > > mailto:jo...@devlieghere.com> 
>> > > <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>> wrote:
>> > >
>> > >
>> > >
>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner > > > <mailto:tanyalatt...@llvm.org>
>> > >

Re: [lldb-dev] LLDB Website

2019-05-06 Thread Jonas Devlieghere via lldb-dev

Friendly ping.

On Fri, May 3, 2019 at 8:58 AM Jonas Devlieghere 
wrote:

> Hey Tanya,
>
> It appears the website is still stuck. It hasn't picked up my changes from
> earlier this week. Please let me know if there's anything I can do to help.
>
> Thanks,
> Jonas
>
> On Wed, May 1, 2019 at 10:40 PM Tanya Lattner 
> wrote:
>
>> I will give this a shot. I did remove the changes before to prevent any
>> issue.
>>
>> -Tanya
>>
>> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere 
>> wrote:
>>
>> I've merged the aforementioned patch.
>>
>> Tanya, can you give generating the python docs another shot?
>>
>> Thanks,
>> Jonas
>>
>> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere 
>> wrote:
>>
>>> I've put up a patch to make it possible to generate the python reference
>>> without building lldb at all: https://reviews.llvm.org/D61216
>>>
>>> PS: The website isn't updating anymore, is that because of the python
>>> reference generation?
>>>
>>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward 
>>> wrote:
>>>
>>>> That's the issue - lldb-python-doc depends on liblldb. From
>>>> docs/CMakeLists.txt:
>>>>
>>>> if(EPYDOC_EXECUTABLE)
>>>>   find_program(DOT_EXECUTABLE dot)
>>>> if(DOT_EXECUTABLE)
>>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath
>>>> ${DOT_EXECUTABLE})
>>>> endif()
>>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>>> #set(ENV{PYTHONPATH}
>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>>> add_custom_target(lldb-python-doc
>>>>   ${EPYDOC_EXECUTABLE}
>>>>   --html
>>>>   lldb
>>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>>   --name "LLDB python API"
>>>>   --url "http://lldb.llvm.org;
>>>>   ${EPYDOC_OPTIONS}
>>>>   DEPENDS swig_wrapper liblldb
>>>>   WORKING_DIRECTORY
>>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>>   COMMENT "Generating LLDB Python API reference with epydoc"
>>>> VERBATIM
>>>> )
>>>> endif(EPYDOC_EXECUTABLE)
>>>>
>>>>
>>>> > -Original Message-
>>>> > From: lldb-dev  On Behalf Of Pavel
>>>> Labath
>>>> > via lldb-dev
>>>> > Sent: Wednesday, April 24, 2019 1:16 AM
>>>> > To: Jonas Devlieghere ; Tanya Lattner
>>>> > 
>>>> > Cc: LLDB 
>>>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>>>> >
>>>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>>>> > >
>>>> > >
>>>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>>>> > > mailto:jo...@devlieghere.com>> wrote:
>>>> > >
>>>> > >
>>>> > >
>>>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner <
>>>> tanyalatt...@llvm.org
>>>> > > <mailto:tanyalatt...@llvm.org>> wrote:
>>>> > >
>>>> > >
>>>> > >
>>>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>>>> > >> mailto:jo...@devlieghere.com>>
>>>> wrote:
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
>>>> > >> mailto:tanyalatt...@llvm.org>>
>>>> wrote:
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
>>>> > >>> mailto:jo...@devlieghere.com
>>>> >>
>>>> > wrote:
>>>> > >>>
>>>> > >>> Hey Tanya,
>>>> > >>>
>>>> > >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
>>>> > >>> mailto:tanyalatt...@llvm.org>>
>>>> wrote:
>>>> > >>>
>>>> > >>> Jonas,
>

Re: [lldb-dev] LLDB Website

2019-05-03 Thread Jonas Devlieghere via lldb-dev

Hey Tanya,

It appears the website is still stuck. It hasn't picked up my changes from
earlier this week. Please let me know if there's anything I can do to help.

Thanks,
Jonas

On Wed, May 1, 2019 at 10:40 PM Tanya Lattner  wrote:

> I will give this a shot. I did remove the changes before to prevent any
> issue.
>
> -Tanya
>
> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere 
> wrote:
>
> I've merged the aforementioned patch.
>
> Tanya, can you give generating the python docs another shot?
>
> Thanks,
> Jonas
>
> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere 
> wrote:
>
>> I've put up a patch to make it possible to generate the python reference
>> without building lldb at all: https://reviews.llvm.org/D61216
>>
>> PS: The website isn't updating anymore, is that because of the python
>> reference generation?
>>
>> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward 
>> wrote:
>>
>>> That's the issue - lldb-python-doc depends on liblldb. From
>>> docs/CMakeLists.txt:
>>>
>>> if(EPYDOC_EXECUTABLE)
>>>   find_program(DOT_EXECUTABLE dot)
>>> if(DOT_EXECUTABLE)
>>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath
>>> ${DOT_EXECUTABLE})
>>> endif()
>>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>>> file(MAKE_DIRECTORY "${DOC_DIR}")
>>> #set(ENV{PYTHONPATH}
>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>>> add_custom_target(lldb-python-doc
>>>   ${EPYDOC_EXECUTABLE}
>>>   --html
>>>   lldb
>>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>>   --name "LLDB python API"
>>>   --url "http://lldb.llvm.org;
>>>   ${EPYDOC_OPTIONS}
>>>   DEPENDS swig_wrapper liblldb
>>>   WORKING_DIRECTORY
>>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>>       COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
>>> )
>>> endif(EPYDOC_EXECUTABLE)
>>>
>>>
>>> > -Original Message-
>>> > From: lldb-dev  On Behalf Of Pavel
>>> Labath
>>> > via lldb-dev
>>> > Sent: Wednesday, April 24, 2019 1:16 AM
>>> > To: Jonas Devlieghere ; Tanya Lattner
>>> > 
>>> > Cc: LLDB 
>>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>>> >
>>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>>> > >
>>> > >
>>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>>> > > mailto:jo...@devlieghere.com>> wrote:
>>> > >
>>> > >
>>> > >
>>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner <
>>> tanyalatt...@llvm.org
>>> > > <mailto:tanyalatt...@llvm.org>> wrote:
>>> > >
>>> > >
>>> > >
>>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>>> > >> mailto:jo...@devlieghere.com>>
>>> wrote:
>>> > >>
>>> > >>
>>> > >>
>>> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
>>> > >> mailto:tanyalatt...@llvm.org>>
>>> wrote:
>>> > >>
>>> > >>
>>> > >>
>>> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
>>> > >>> mailto:jo...@devlieghere.com>>
>>> > wrote:
>>> > >>>
>>> > >>> Hey Tanya,
>>> > >>>
>>> > >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
>>> > >>> mailto:tanyalatt...@llvm.org>>
>>> wrote:
>>> > >>>
>>> > >>> 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
>>> > >>>

Re: [lldb-dev] LLDB Website

2019-05-01 Thread Tanya Lattner via lldb-dev

I will give this a shot. I did remove the changes before to prevent any issue.

-Tanya

> On Apr 29, 2019, at 10:26 AM, Jonas Devlieghere  wrote:
> 
> I've merged the aforementioned patch. 
> 
> Tanya, can you give generating the python docs another shot?
> 
> Thanks,
> Jonas
> 
> On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere  <mailto:jo...@devlieghere.com>> wrote:
> I've put up a patch to make it possible to generate the python reference 
> without building lldb at all: https://reviews.llvm.org/D61216 
> <https://reviews.llvm.org/D61216>
> 
> PS: The website isn't updating anymore, is that because of the python 
> reference generation?
> 
> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward  <mailto:tedw...@quicinc.com>> wrote:
> That's the issue - lldb-python-doc depends on liblldb. From 
> docs/CMakeLists.txt:
> 
> if(EPYDOC_EXECUTABLE)
>   find_program(DOT_EXECUTABLE dot)
> if(DOT_EXECUTABLE)
>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
> ${DOT_EXECUTABLE})
> endif()
> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
> file(MAKE_DIRECTORY "${DOC_DIR}")
> #set(ENV{PYTHONPATH} 
> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
> add_custom_target(lldb-python-doc
>   ${EPYDOC_EXECUTABLE}
>   --html
>   lldb
>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>   --name "LLDB python API"
>   --url "http://lldb.llvm.org <http://lldb.llvm.org/>"
>   ${EPYDOC_OPTIONS}
>   DEPENDS swig_wrapper liblldb
>   WORKING_DIRECTORY 
> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
> )
> endif(EPYDOC_EXECUTABLE)
> 
> 
> > -Original Message-
> > From: lldb-dev  > <mailto:lldb-dev-boun...@lists.llvm.org>> On Behalf Of Pavel Labath
> > via lldb-dev
> > Sent: Wednesday, April 24, 2019 1:16 AM
> > To: Jonas Devlieghere  > <mailto:jo...@devlieghere.com>>; Tanya Lattner
> > mailto:tanyalatt...@llvm.org>>
> > Cc: LLDB mailto:lldb-dev@lists.llvm.org>>
> > Subject: [EXT] Re: [lldb-dev] LLDB Website
> > 
> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
> > >
> > >
> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
> > > mailto:jo...@devlieghere.com> 
> > > <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>> wrote:
> > >
> > >
> > >
> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner  > > <mailto:tanyalatt...@llvm.org>
> > > <mailto:tanyalatt...@llvm.org <mailto:tanyalatt...@llvm.org>>> wrote:
> > >
> > >
> > >
> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
> > >> mailto:jo...@devlieghere.com> 
> > >> <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>> wrote:
> > >>
> > >>
> > >>
> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
> > >> mailto:tanyalatt...@llvm.org> 
> > >> <mailto:tanyalatt...@llvm.org <mailto:tanyalatt...@llvm.org>>> wrote:
> > >>
> > >>
> > >>
> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
> > >>> mailto:jo...@devlieghere.com> 
> > >>> <mailto:jo...@devlieghere.com <mailto:jo...@devlieghere.com>>>
> > wrote:
> > >>>
> > >>> Hey Tanya,
> > >>>
> > >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
> > >>> mailto:tanyalatt...@llvm.org> 
> > >>> <mailto:tanyalatt...@llvm.org <mailto:tanyalatt...@llvm.org>>> wrote:
> > >>>
> > >>> 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?
> > >>>
> > >>> That sounds perfect. Can we still do the regular website
> > >

Re: [lldb-dev] LLDB Website

2019-04-29 Thread Jonas Devlieghere via lldb-dev

I've merged the aforementioned patch.

Tanya, can you give generating the python docs another shot?

Thanks,
Jonas

On Fri, Apr 26, 2019 at 4:29 PM Jonas Devlieghere 
wrote:

> I've put up a patch to make it possible to generate the python reference
> without building lldb at all: https://reviews.llvm.org/D61216
>
> PS: The website isn't updating anymore, is that because of the python
> reference generation?
>
> On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward  wrote:
>
>> That's the issue - lldb-python-doc depends on liblldb. From
>> docs/CMakeLists.txt:
>>
>> if(EPYDOC_EXECUTABLE)
>>   find_program(DOT_EXECUTABLE dot)
>> if(DOT_EXECUTABLE)
>>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath
>> ${DOT_EXECUTABLE})
>> endif()
>> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
>> file(MAKE_DIRECTORY "${DOC_DIR}")
>> #set(ENV{PYTHONPATH}
>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
>> add_custom_target(lldb-python-doc
>>   ${EPYDOC_EXECUTABLE}
>>   --html
>>   lldb
>>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>>   --name "LLDB python API"
>>   --url "http://lldb.llvm.org;
>>   ${EPYDOC_OPTIONS}
>>   DEPENDS swig_wrapper liblldb
>>   WORKING_DIRECTORY
>> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
>> )
>> endif(EPYDOC_EXECUTABLE)
>>
>>
>> > -Original Message-
>> > From: lldb-dev  On Behalf Of Pavel
>> Labath
>> > via lldb-dev
>> > Sent: Wednesday, April 24, 2019 1:16 AM
>> > To: Jonas Devlieghere ; Tanya Lattner
>> > 
>> > Cc: LLDB 
>> > Subject: [EXT] Re: [lldb-dev] LLDB Website
>> >
>> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
>> > >
>> > >
>> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
>> > > mailto:jo...@devlieghere.com>> wrote:
>> > >
>> > >
>> > >
>> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner <
>> tanyalatt...@llvm.org
>> > > <mailto:tanyalatt...@llvm.org>> wrote:
>> > >
>> > >
>> > >
>> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
>> > >> mailto:jo...@devlieghere.com>>
>> wrote:
>> > >>
>> > >>
>> > >>
>> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
>> > >> mailto:tanyalatt...@llvm.org>>
>> wrote:
>> > >>
>> > >>
>> > >>
>> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
>> > >>> mailto:jo...@devlieghere.com>>
>> > wrote:
>> > >>>
>> > >>> Hey Tanya,
>> > >>>
>> > >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
>> > >>> mailto:tanyalatt...@llvm.org>>
>> wrote:
>> > >>>
>> > >>> 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?
>> > >>>
>> > >>> That sounds perfect. Can we still do the regular website
>> > >>> post commit?
>> > >>
>> > >> Yes, so it will do docs-lldb-html on every commit.
>> > >>
>> > >>
>> > >> Perfect!
>> > >>
>> > >>
>> > >> So I am able to generate the cpp reference docs:
>> > >> https://lldb.llvm.org/cpp_reference/index.html
>> > >>
>> > >> However, the main website links to
>> > >> https://lldb.llvm.org/cpp_reference/html/index.html. Do
>> > >> you want the html in that url?

Re: [lldb-dev] LLDB Website

2019-04-26 Thread Jonas Devlieghere via lldb-dev

I've put up a patch to make it possible to generate the python reference
without building lldb at all: https://reviews.llvm.org/D61216

PS: The website isn't updating anymore, is that because of the python
reference generation?

On Wed, Apr 24, 2019 at 11:46 AM Ted Woodward  wrote:

> That's the issue - lldb-python-doc depends on liblldb. From
> docs/CMakeLists.txt:
>
> if(EPYDOC_EXECUTABLE)
>   find_program(DOT_EXECUTABLE dot)
> if(DOT_EXECUTABLE)
>   set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath
> ${DOT_EXECUTABLE})
> endif()
> set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
> file(MAKE_DIRECTORY "${DOC_DIR}")
> #set(ENV{PYTHONPATH}
> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
> add_custom_target(lldb-python-doc
>   ${EPYDOC_EXECUTABLE}
>   --html
>   lldb
>   -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
>   --name "LLDB python API"
>   --url "http://lldb.llvm.org;
>   ${EPYDOC_OPTIONS}
>   DEPENDS swig_wrapper liblldb
>   WORKING_DIRECTORY
> ${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
>   COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
> )
> endif(EPYDOC_EXECUTABLE)
>
>
> > -Original Message-
> > From: lldb-dev  On Behalf Of Pavel
> Labath
> > via lldb-dev
> > Sent: Wednesday, April 24, 2019 1:16 AM
> > To: Jonas Devlieghere ; Tanya Lattner
> > 
> > Cc: LLDB 
> > Subject: [EXT] Re: [lldb-dev] LLDB Website
> >
> > On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
> > >
> > >
> > > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
> > > mailto:jo...@devlieghere.com>> wrote:
> > >
> > >
> > >
> > > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner <
> tanyalatt...@llvm.org
> > > <mailto:tanyalatt...@llvm.org>> wrote:
> > >
> > >
> > >
> > >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
> > >> mailto:jo...@devlieghere.com>> wrote:
> > >>
> > >>
> > >>
> > >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
> > >> mailto:tanyalatt...@llvm.org>> wrote:
> > >>
> > >>
> > >>
> > >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
> > >>> mailto:jo...@devlieghere.com>>
> > wrote:
> > >>>
> > >>> Hey Tanya,
> > >>>
> > >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
> > >>> mailto:tanyalatt...@llvm.org>>
> wrote:
> > >>>
> > >>> 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?
> > >>>
> > >>> That sounds perfect. Can we still do the regular website
> > >>> post commit?
> > >>
> > >> Yes, so it will do docs-lldb-html on every commit.
> > >>
> > >>
> > >> Perfect!
> > >>
> > >>
> > >> So I am able to generate the cpp reference docs:
> > >> https://lldb.llvm.org/cpp_reference/index.html
> > >>
> > >> However, the main website links to
> > >> https://lldb.llvm.org/cpp_reference/html/index.html. Do
> > >> you want the html in that url? I can change the alias. We
> > >> strip for other doxygen.
> > >>
> > >>
> > >> Let's keep it without the html. I'll update a link on the
> > >> website and add a redirect.
> > >>
> > >>
> > >> As for python docs, what is required to build those? It's
> > >> not showing up as a target for me.
> > >>
> > >>
> > >> This is probably because you don't have `epydoc` installed
> > >> (sudo pip insta

Re: [lldb-dev] LLDB Website

2019-04-24 Thread Ted Woodward via lldb-dev

That's the issue - lldb-python-doc depends on liblldb. From docs/CMakeLists.txt:

if(EPYDOC_EXECUTABLE)
  find_program(DOT_EXECUTABLE dot)
if(DOT_EXECUTABLE)
  set(EPYDOC_OPTIONS ${EPYDOC_OPTIONS} --graph all --dotpath 
${DOT_EXECUTABLE})
endif()
set(DOC_DIR "${CMAKE_CURRENT_SOURCE_DIR}/doc")
file(MAKE_DIRECTORY "${DOC_DIR}")
#set(ENV{PYTHONPATH} 
${CMAKE_CURRENT_BINARY_DIR}/../../../lib/python2.7/site-packages)
add_custom_target(lldb-python-doc
  ${EPYDOC_EXECUTABLE}
  --html
  lldb
  -o ${CMAKE_CURRENT_BINARY_DIR}/python_reference
  --name "LLDB python API"
  --url "http://lldb.llvm.org;
  ${EPYDOC_OPTIONS}
  DEPENDS swig_wrapper liblldb
  WORKING_DIRECTORY 
${CMAKE_CURRENT_BINARY_DIR}/../../../lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages
  COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM
)
endif(EPYDOC_EXECUTABLE)


> -Original Message-
> From: lldb-dev  On Behalf Of Pavel Labath
> via lldb-dev
> Sent: Wednesday, April 24, 2019 1:16 AM
> To: Jonas Devlieghere ; Tanya Lattner
> 
> Cc: LLDB 
> Subject: [EXT] Re: [lldb-dev] LLDB Website
> 
> On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:
> >
> >
> > On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere
> > mailto:jo...@devlieghere.com>> wrote:
> >
> >
> >
> > On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner  > <mailto:tanyalatt...@llvm.org>> wrote:
> >
> >
> >
> >> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
> >> mailto:jo...@devlieghere.com>> wrote:
> >>
> >>
> >>
> >> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
> >> mailto:tanyalatt...@llvm.org>> wrote:
> >>
> >>
> >>
> >>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
> >>> mailto:jo...@devlieghere.com>>
> wrote:
> >>>
> >>> Hey Tanya,
> >>>
> >>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
> >>> mailto:tanyalatt...@llvm.org>> wrote:
> >>>
> >>> 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?
> >>>
> >>> That sounds perfect. Can we still do the regular website
> >>> post commit?
> >>
> >> Yes, so it will do docs-lldb-html on every commit.
> >>
> >>
> >> Perfect!
> >>
> >>
> >> So I am able to generate the cpp reference docs:
> >> https://lldb.llvm.org/cpp_reference/index.html
> >>
> >> However, the main website links to
> >> https://lldb.llvm.org/cpp_reference/html/index.html. Do
> >> you want the html in that url? I can change the alias. We
> >> strip for other doxygen.
> >>
> >>
> >> Let's keep it without the html. I'll update a link on the
> >> website and add a redirect.
> >>
> >>
> >> As for python docs, what is required to build those? It's
> >> not showing up as a target for me.
> >>
> >>
> >> This is probably because you don't have `epydoc` installed
> >> (sudo pip install epydoc).
> >> I think you'll have to re-run cmake after for it to pick it
> >> up. The corresponding target should then be `lldb-python-doc`.
> >>
> >> https://lldb.llvm.org/cpp_reference/index.html
> >
> > Well installing epydoc did the trick, but I don’t think the
> > doxygen script is the right place for this target. I have not
> > dug into it yet but it appears to require some LLVM libraries
> > and is building those. I’m letting it finish to verify it builds
> > but I’ll have to sort out the best way of doing this on the
> > server. We have other scripts that generate other documentation
> > that build parts of LLVM. Ideally, I would want to leverage that
> > and red

Re: [lldb-dev] LLDB Website

2019-04-24 Thread Pavel Labath via lldb-dev


On 24/04/2019 03:19, Jonas Devlieghere via lldb-dev wrote:



On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere > wrote:




On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner mailto:tanyalatt...@llvm.org>> wrote:




On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere
mailto:jo...@devlieghere.com>> wrote:



On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner
mailto:tanyalatt...@llvm.org>> wrote:




On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere
mailto:jo...@devlieghere.com>> wrote:

Hey Tanya,

On Tue, Apr 23, 2019 at 11:51 Tanya Lattner
mailto:tanyalatt...@llvm.org>> wrote:

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?

That sounds perfect. Can we still do the regular website
post commit? 


Yes, so it will do docs-lldb-html on every commit.


Perfect!


So I am able to generate the cpp reference docs:
https://lldb.llvm.org/cpp_reference/index.html

However, the main website links to
https://lldb.llvm.org/cpp_reference/html/index.html. Do
you want the html in that url? I can change the alias. We
strip for other doxygen.


Let's keep it without the html. I'll update a link on the
website and add a redirect.


As for python docs, what is required to build those? It's
not showing up as a target for me.


This is probably because you don't have `epydoc` installed
(sudo pip install epydoc).
I think you'll have to re-run cmake after for it to pick it
up. The corresponding target should then be `lldb-python-doc`.

https://lldb.llvm.org/cpp_reference/index.html


Well installing epydoc did the trick, but I don’t think the
doxygen script is the right place for this target. I have not
dug into it yet but it appears to require some LLVM libraries
and is building those. I’m letting it finish to verify it builds
but I’ll have to sort out the best way of doing this on the
server. We have other scripts that generate other documentation
that build parts of LLVM. Ideally, I would want to leverage that
and reduce build times.


Yeah, the annoying thing about the Python documentation is that it
builds the C++ API, then runs swig to generate the Python wrapper,
and finally generates the docs from that.


It should be possible to solve this by tweaking the dependency graph a 
bit. There's no fundamental reason why you need to build anything in 
order to run swig. It is purely a textual step -- it ingests header 
files and interface definitions and spits out python and cpp files. The 
inputs are present as static checked in source, so the swig step could 
theoretically be the very first build command that we run.



I wonder if we can just use the static bindings that are checked-in
instead. I will look into that later today/tomorrow. 



Right, so the reason is that we don't have the static bindings on 
llvm.org  (we have them for swift-lldb on GitHub).
Maybe we should check them in upstream too? That's something the 
community will have to weigh in on...




I think it would be good to avoid that...

pl
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Jonas Devlieghere via lldb-dev

On Tue, Apr 23, 2019 at 6:04 PM Jonas Devlieghere 
wrote:

>
>
> On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner 
> wrote:
>
>>
>>
>> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere 
>> wrote:
>>
>>
>>
>> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner 
>> wrote:
>>
>>>
>>>
>>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere 
>>> wrote:
>>>
>>> Hey Tanya,
>>>
>>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner 
>>> wrote:
>>>
 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?

>>>
>>> That sounds perfect. Can we still do the regular website post commit?
>>>
>>>
>>> Yes, so it will do docs-lldb-html on every commit.
>>>
>>
>> Perfect!
>>
>>
>>>
>>> So I am able to generate the cpp reference docs:
>>> https://lldb.llvm.org/cpp_reference/index.html
>>>
>>> However, the main website links to
>>> https://lldb.llvm.org/cpp_reference/html/index.html. Do you want the
>>> html in that url? I can change the alias. We strip for other doxygen.
>>>
>>
>> Let's keep it without the html. I'll update a link on the website and add
>> a redirect.
>>
>>
>>>
>>> As for python docs, what is required to build those? It's not showing up
>>> as a target for me.
>>>
>>
>> This is probably because you don't have `epydoc` installed (sudo pip
>> install epydoc).
>> I think you'll have to re-run cmake after for it to pick it up. The
>> corresponding target should then be `lldb-python-doc`.
>>
>> https://lldb.llvm.org/cpp_reference/index.html
>>
>>
>> Well installing epydoc did the trick, but I don’t think the doxygen
>> script is the right place for this target. I have not dug into it yet but
>> it appears to require some LLVM libraries and is building those. I’m
>> letting it finish to verify it builds but I’ll have to sort out the best
>> way of doing this on the server. We have other scripts that generate other
>> documentation that build parts of LLVM. Ideally, I would want to leverage
>> that and reduce build times.
>>
>
> Yeah, the annoying thing about the Python documentation is that it builds
> the C++ API, then runs swig to generate the Python wrapper, and finally
> generates the docs from that.
> I wonder if we can just use the static bindings that are checked-in
> instead. I will look into that later today/tomorrow.
>

Right, so the reason is that we don't have the static bindings on llvm.org
(we have them for swift-lldb on GitHub).
Maybe we should check them in upstream too? That's something the community
will have to weigh in on...


>
>
>>
>> -Tanya
>>
>>
>>
>>>
>>> Thanks,
>>> Tanya
>>>
>>
>> Thanks again for doing this.
>>
>> Cheers,
>> Jonas
>>
>>
>>>
>>>
>>>
>>>
 -Tanya

>>>
>>> Thank you!
>>>
>>>
 On Apr 23, 2019, at 11:45 AM, Tanya Lattner 
 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 
 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.

 Also, as the result of this change the following two links are broken:

 https://lldb.llvm.org/cpp_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.



 --
>>> Sent from my iPhone
>>>
>>>
>>>
>>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Jonas Devlieghere via lldb-dev

On Tue, Apr 23, 2019 at 5:43 PM Tanya Lattner  wrote:

>
>
> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere 
> wrote:
>
>
>
> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner 
> wrote:
>
>>
>>
>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere 
>> wrote:
>>
>> Hey Tanya,
>>
>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner 
>> wrote:
>>
>>> 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?
>>>
>>
>> That sounds perfect. Can we still do the regular website post commit?
>>
>>
>> Yes, so it will do docs-lldb-html on every commit.
>>
>
> Perfect!
>
>
>>
>> So I am able to generate the cpp reference docs:
>> https://lldb.llvm.org/cpp_reference/index.html
>>
>> However, the main website links to
>> https://lldb.llvm.org/cpp_reference/html/index.html. Do you want the
>> html in that url? I can change the alias. We strip for other doxygen.
>>
>
> Let's keep it without the html. I'll update a link on the website and add
> a redirect.
>
>
>>
>> As for python docs, what is required to build those? It's not showing up
>> as a target for me.
>>
>
> This is probably because you don't have `epydoc` installed (sudo pip
> install epydoc).
> I think you'll have to re-run cmake after for it to pick it up. The
> corresponding target should then be `lldb-python-doc`.
>
> https://lldb.llvm.org/cpp_reference/index.html
>
>
> Well installing epydoc did the trick, but I don’t think the doxygen script
> is the right place for this target. I have not dug into it yet but it
> appears to require some LLVM libraries and is building those. I’m letting
> it finish to verify it builds but I’ll have to sort out the best way of
> doing this on the server. We have other scripts that generate other
> documentation that build parts of LLVM. Ideally, I would want to leverage
> that and reduce build times.
>

Yeah, the annoying thing about the Python documentation is that it builds
the C++ API, then runs swig to generate the Python wrapper, and finally
generates the docs from that.
I wonder if we can just use the static bindings that are checked-in
instead. I will look into that later today/tomorrow.


>
> -Tanya
>
>
>
>>
>> Thanks,
>> Tanya
>>
>
> Thanks again for doing this.
>
> Cheers,
> Jonas
>
>
>>
>>
>>
>>
>>> -Tanya
>>>
>>
>> Thank you!
>>
>>
>>> On Apr 23, 2019, at 11:45 AM, Tanya Lattner 
>>> 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 
>>> 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.
>>>
>>> Also, as the result of this change the following two links are broken:
>>>
>>> https://lldb.llvm.org/cpp_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.
>>>
>>>
>>>
>>> --
>> Sent from my iPhone
>>
>>
>>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Tanya Lattner via lldb-dev



> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere  wrote:
> 
> 
> 
> On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner  > wrote:
> 
> 
>> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere > > wrote:
>> 
>> Hey Tanya,
>> 
>> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner > > wrote:
>> 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?
>>   
>> That sounds perfect. Can we still do the regular website post commit? 
> 
> Yes, so it will do docs-lldb-html on every commit.
> 
> Perfect! 
>  
> 
> So I am able to generate the cpp reference docs: 
> https://lldb.llvm.org/cpp_reference/index.html 
> 
> 
> However, the main website links to 
> https://lldb.llvm.org/cpp_reference/html/index.html 
> . Do you want the html 
> in that url? I can change the alias. We strip for other doxygen.
> 
> Let's keep it without the html. I'll update a link on the website and add a 
> redirect. 
>  
> 
> As for python docs, what is required to build those? It's not showing up as a 
> target for me.
> 
> This is probably because you don't have `epydoc` installed (sudo pip install 
> epydoc). 
> I think you'll have to re-run cmake after for it to pick it up. The 
> corresponding target should then be `lldb-python-doc`. 
> 
> https://lldb.llvm.org/cpp_reference/index.html 
> 
Well installing epydoc did the trick, but I don’t think the doxygen script is 
the right place for this target. I have not dug into it yet but it appears to 
require some LLVM libraries and is building those. I’m letting it finish to 
verify it builds but I’ll have to sort out the best way of doing this on the 
server. We have other scripts that generate other documentation that build 
parts of LLVM. Ideally, I would want to leverage that and reduce build times.

-Tanya
>  
> 
> Thanks,
> Tanya
> 
> Thanks again for doing this.
> 
> Cheers,
> Jonas
>  
> 
> 
>> 
>> 
>> -Tanya
>> 
>> Thank you! 
>> 
>> 
>>> On Apr 23, 2019, at 11:45 AM, Tanya Lattner >> > 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 >>> > 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 
 . 
 
 Also, as the result of this change the following two links are broken:
 
 https://lldb.llvm.org/cpp_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. 
>>> 
>> 
>> -- 
>> Sent from my iPhone
> 

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Jonas Devlieghere via lldb-dev

On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner  wrote:

>
>
> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere 
> wrote:
>
> Hey Tanya,
>
> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner  wrote:
>
>> 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?
>>
>
> That sounds perfect. Can we still do the regular website post commit?
>
>
> Yes, so it will do docs-lldb-html on every commit.
>

Perfect!


>
> So I am able to generate the cpp reference docs:
> https://lldb.llvm.org/cpp_reference/index.html
>
> However, the main website links to
> https://lldb.llvm.org/cpp_reference/html/index.html. Do you want the html
> in that url? I can change the alias. We strip for other doxygen.
>

Let's keep it without the html. I'll update a link on the website and add a
redirect.


>
> As for python docs, what is required to build those? It's not showing up
> as a target for me.
>

This is probably because you don't have `epydoc` installed (sudo pip
install epydoc).
I think you'll have to re-run cmake after for it to pick it up. The
corresponding target should then be `lldb-python-doc`.

https://lldb.llvm.org/cpp_reference/index.html


>
> Thanks,
> Tanya
>

Thanks again for doing this.

Cheers,
Jonas


>
>
>
>
>> -Tanya
>>
>
> Thank you!
>
>
>> On Apr 23, 2019, at 11:45 AM, Tanya Lattner 
>> 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 
>> 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.
>>
>> Also, as the result of this change the following two links are broken:
>>
>> https://lldb.llvm.org/cpp_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.
>>
>>
>>
>> --
> Sent from my iPhone
>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Tanya Lattner via lldb-dev



> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere  wrote:
> 
> Hey Tanya,
> 
> On Tue, Apr 23, 2019 at 11:51 Tanya Lattner  > wrote:
> 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?
>   
> That sounds perfect. Can we still do the regular website post commit? 

Yes, so it will do docs-lldb-html on every commit.

So I am able to generate the cpp reference docs: 
https://lldb.llvm.org/cpp_reference/index.html

However, the main website links to 
https://lldb.llvm.org/cpp_reference/html/index.html. Do you want the html in 
that url? I can change the alias. We strip for other doxygen.

As for python docs, what is required to build those? It's not showing up as a 
target for me.

Thanks,
Tanya





> 
> 
> -Tanya
> 
> Thank you! 
> 
> 
>> On Apr 23, 2019, at 11:45 AM, Tanya Lattner > > 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 >> > 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 
>>> . 
>>> 
>>> Also, as the result of this change the following two links are broken:
>>> 
>>> https://lldb.llvm.org/cpp_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. 
>> 
> 
> -- 
> Sent from my iPhone

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Jonas Devlieghere via lldb-dev

Hey Tanya,

On Tue, Apr 23, 2019 at 11:51 Tanya Lattner  wrote:

> 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?
>

That sounds perfect. Can we still do the regular website post commit?


> -Tanya
>

Thank you!


> On Apr 23, 2019, at 11:45 AM, Tanya Lattner  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 
> 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.
>
> Also, as the result of this change the following two links are broken:
>
> https://lldb.llvm.org/cpp_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.
>
>
>
> --
Sent from my iPhone
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Tanya Lattner via lldb-dev

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  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 > > 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 
>> . 
>> 
>> Also, as the result of this change the following two links are broken:
>> 
>> https://lldb.llvm.org/cpp_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

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Tanya Lattner via lldb-dev

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  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 
> . 
> 
> Also, as the result of this change the following two links are broken:
> 
> https://lldb.llvm.org/cpp_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

Re: [lldb-dev] LLDB Website

2019-04-23 Thread Jonas Devlieghere via lldb-dev

Friendly ping.

There's a bunch of people that are annoyed by the missing documentation.
I've already addressed most of the other comments about the broken URLs and
missing top level links, but unfortunately that doesn't take effect because
the website isn't updating.

On Fri, Apr 19, 2019 at 12:17 PM Jonas Devlieghere 
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.
>
> Also, as the result of this change the following two links are broken:
>
> https://lldb.llvm.org/cpp_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,
> 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

[lldb-dev] LLDB Website

2019-04-19 Thread Jonas Devlieghere via lldb-dev

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.

Also, as the result of this change the following two links are broken:

https://lldb.llvm.org/cpp_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,
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

Re: [lldb-dev] LLDB Website is not being updated

Re: [lldb-dev] LLDB Website is not being updated

Re: [lldb-dev] LLDB Website is not being updated

Re: [lldb-dev] LLDB Website is not being updated

Re: [lldb-dev] LLDB Website is not being updated

Re: [lldb-dev] LLDB Website is not being updated

[lldb-dev] LLDB Website is not being updated

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

Re: [lldb-dev] LLDB Website

[lldb-dev] LLDB Website

31 matches

Site Navigation

Mail list logo

Footer information