[Paraview] Secrets of the ParaView install process

[Michael Jackson]

Without digging deeper into the Qt Assistant problem I know that there  
was a slight name change from Qt 4.3 to Qt 4.4 for the QtAssistant. I  
think it is called "Assistant_adp" now. So check your Qt version and  
see if that might be the problem.

_________________________________________________________
Mike Jackson                  mike.jackson at bluequartz.net
BlueQuartz Software                    www.bluequartz.net
Principal Software Engineer                  Dayton, Ohio



On May 18, 2009, at 6:05 AM, John Biddiscombe wrote:

> After some experimentation, python now works (astonished surprise) -  
> the main trick appear to be to cpoy the python lib dir structure  
> into the correct relative place in the install tree.
>
> qt-assistant still does not work. The assisstant help issue appears  
> to be caused by paraview invoking the wrong command line, but I  
> don't understand why.
>
> Also...I forgot to ask first time around.
> why are the iceT DLLs installed into lib when all other dlls are  
> installed into the bin directory. (Is this a simple mistake, or is  
> ther a real reason?)
>
> JB
>> I tried to create an install package of (tweaked) paraview +  
>> plugins on windows.
>>
>> All runs fine except that
>> 1) Python dlls (etc) are not included in the distribution
>> 2) QtAssistant won't run - so help is unavailable.
>>
>> Are there special tricks required to make paraview include the  
>> necessary python dll's (and init scripts?) - I'm using python 2.6.  
>> I notice that the paraview 3.4 release on the kitware website uses  
>> python 2.5. Should I revert to 2.5 to solve the problem. Are things  
>> 'hard coded' for 2.5 that don't work for 2.6.
>> If I use the zip installer, I can manually add python libs to the  
>> distribution, if I uses the NSIS installer I cannot. The  
>> ParaView3.4 release uses NSIS - so was some secret process involved  
>> in adding these files?
>>
>> For QtAssistant, I don't know why it won't run. any clues welcome  
>> (path?)
>>
>> NB. I have not set any
>> PATH,
>> PV_PLUGIN_PATH,
>> PYTHON_XXX_???
>>
>> Variables. should I setup a batch file which initializes these and  
>> then calls paraview (plugins load fine if they are in the plugins  
>> directory)
>>
>> Many thanks
>>
>> JB
>>
>
>
> -- 
> John Biddiscombe,                            email:biddisco @ cscs.ch
> http://www.cscs.ch/
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
> Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82
>
>
> _______________________________________________
> 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