[Paraview] Fedora mpi packaging
Berk Geveci
berk.geveci at kitware.com
Thu Jun 26 15:23:23 EDT 2008
Although it would make sense to separate the two, it would probably
require duplication of some files. The client would have paraview and
pvpython, the server pvbatch, pvserver, pvdataserver, pvrenderserver.
However, pvpython and pvbatch both depend on some .py files. To do it
really right, you would have to do something like:
* ParaView python core - all .py files (this package is useless by itself)
* ParaView client (paraview and pvpython) depends on python, Qt and
ParaView python core
* ParaView server (pvbatch, pvserver, pvdataserver, pvrenderserver)
depends on python, mpi and ParaView python core
I may be missing some dependencies here...
-berk
On Thu, Jun 26, 2008 at 2:02 PM, Orion Poplawski <orion at cora.nwra.com> wrote:
> Kent Eschenberg wrote:
>>
>> Orion Poplawski wrote:
>>>
>>> My current question is what binaries need mpi versions? ...
>>> But I'm guessing you could use a non-mpi "paraview" binary to connect to
>>> a parallel running pvserver just fine ...
>>
>> Yes. I don't think the mpi version of "paraview" actually uses mpi. You
>> definitely need the mpi version of pvbatch and pvserver; I don't know about
>> the others.
>>
>> Kent
>> Pittsburgh Supercomputing Center
>
> Follow up -
>
> Would it make sense to have "client" and "server" packages? If so, what
> would go where?
>
> Thanks!
>
> --
> Orion Poplawski
> Technical Manager 303-415-9701 x222
> NWRA/CoRA Division FAX: 303-415-9702
> 3380 Mitchell Lane orion at cora.nwra.com
> Boulder, CO 80301 http://www.cora.nwra.com
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>
More information about the ParaView
mailing list