[Paraview] ParaViewFilters.html missing?

[Utkarsh Ayachit]

Well, try to removing your current ParaViewBin/Documentation dir so
that dependencies are setup correctly.

Utkarsh

On Mon, Mar 22, 2010 at 2:02 PM, Michael Jackson
<mike.jackson at bluequartz.net> wrote:
> Thanks, but still get the same error.
> --
> Mike Jackson <www.bluequartz.net>
>
> On Mar 22, 2010, at 1:45 PM, Utkarsh Ayachit wrote:
>
>> Interesting. I thing I added the dependency on the wrong target -- I
>> made the target that compiled the qhp file to depend on the generate
>> the the proxy documentation htmls, but the html files need to be
>> listed in the qhp file in the first place to get compiled in. Fixed
>> that by adding dependencies so that the qhp file is generated after
>> HTMLDocumentation target is built.
>>
>> /cvsroot/ParaView3/ParaView3/Documentation/CMakeLists.txt,v  <--
>> Documentation/CMakeLists.txt
>> new revision: 1.30; previous revision: 1.29
>>
>> Utkarsh
>>
>> On Mon, Mar 22, 2010 at 1:12 PM, Eric E. Monson <emonson at cs.duke.edu>
>> wrote:
>>>
>>> When you do a "make install" it does include the paraview.qch file in
>>> [install]/doc/ but it looks like you're right that the filters and sources
>>> help is not being included in this even though the ParaViewFilters.html and
>>> ParaViewSources.html are being generated properly in the
>>> [build]/Documentation/ directory. (The [build]/Documentation/paraview.qch
>>> file doesn't include the Filters or Sources info, either.)
>>>
>>> I wonder if things are just being generated in the wrong order? (html
>>> after qch instead of the other way around)
>>>
>>> -Eric
>>>
>>>
>>> On Mar 22, 2010, at 12:45 PM, Michael Jackson wrote:
>>>
>>>> Walking through the source code it seems that the entire "paraview.qch"
>>>> file is pushed into a ".cxx" file which is then directly compiled into
>>>> ParaView. Ok. When I click on the "?" button for the Sphere source I get the
>>>> following in a pop up window:
>>>>
>>>> QTextBrowser: No document for
>>>> qthelp://paraview.org/paraview/SphereSource.html
>>>>
>>>> Any help with this would be great. If there is a bug I'll post the
>>>> patch...
>>>> --
>>>> Mike Jackson <www.bluequartz.net>
>>>>
>>>> On Mar 8, 2010, at 9:44 AM, Utkarsh Ayachit wrote:
>>>>
>>>>> BUILD_DOCUMENTATION refers to  the doxygen documentation for the C++
>>>>> classes etc., and never referred to  the help in ParaView.
>>>>>
>>>>> Utkarsh
>>>>>
>>>>> On Mon, Mar 8, 2010 at 9:38 AM, Eric E. Monson <emonson at cs.duke.edu>
>>>>> wrote:
>>>>>>
>>>>>> Okay, so in the past it only got generated when BUILD_DOCUMENTATION
>>>>>> was ON, or was there some other process?
>>>>>>
>>>>>> Thanks for the quick fix,
>>>>>> -Eric
>>>>>>
>>>>>>
>>>>>> On Mar 8, 2010, at 9:35 AM, Utkarsh Ayachit wrote:
>>>>>>
>>>>>>> Eric,
>>>>>>>
>>>>>>> I've committed a fix to CVS. Added is a new advanced CMake variable
>>>>>>> GENERATE_FILTERS_DOCUMENTATION which ensures that the documentation
>>>>>>> for sources/readers etc. is built. It's off by default, since
>>>>>>> many-a-times esp. on windows, running the documentation building
>>>>>>> executable fails due to incomplete PATH etc. which can be very
>>>>>>> annoying.
>>>>>>>
>>>>>>> /cvsroot/ParaView3/ParaView3/Documentation/CMakeLists.txt,v  <--
>>>>>>> Documentation/CMakeLists.txt
>>>>>>> new revision: 1.25; previous revision: 1.24
>>>>>>>
>>>>>>> Utkarsh
>>>>>>>
>>>>>>> On Mon, Mar 8, 2010 at 9:22 AM, Eric E. Monson <emonson at cs.duke.edu>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hey all,
>>>>>>>>
>>>>>>>> In CVS the Documentation/ParaViewFilters.html file is missing, along
>>>>>>>> with all of the individual filters docs. Is this something that gets
>>>>>>>> auto-generated when you turn on BUILD_DOCUMENTATION, or has it really been
>>>>>>>> misplaced? (I usually have doc gen turned off).
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> -Eric
>>>>>>>>
>>>>>>>> ------------------------------------------------------
>>>>>>>> Eric E Monson
>>>>>>>> Duke Visualization Technology Group
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Powered by www.kitware.com
>>>>>>>>
>>>>>>>> Visit other Kitware open-source projects at
>>>>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>>>>
>>>>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>>>>> http://paraview.org/Wiki/ParaView
>>>>>>>>
>>>>>>>> Follow this link to subscribe/unsubscribe:
>>>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>>>>
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>
>>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>>> http://paraview.org/Wiki/ParaView
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the ParaView Wiki at:
>>>> http://paraview.org/Wiki/ParaView
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>