[Paraview] MPI Compilation Flags
Berk Geveci
berk.geveci at kitware.com
Thu Apr 3 20:31:15 EDT 2008
Hmmm. It sounds like you need to use the cross-compilation support we have been
on. We already built paraview on Xt3 and Blue Gene using it. The idea there is
that you first build a small subset of ParaView using the native
compilers and then
use the generators from that to build paraview for another target. I
can point you
to some documentation if you are interested.
-berk
On Thu, Apr 3, 2008 at 5:33 PM, Sean Ziegeler
<seanzig at users.sourceforge.net> wrote:
> At one time I didn't mind looking through, e.g., an "mpicxx" script, to
> figure out the flags to compile MPI programs for a given platform. That is
> getting harder and harder to do now. I did it for IBM AIX, but recently
> I've been trying to build MPI-enabled ParaView on a Cray XT4, and the
> scripts are very involved. Worse, in some versions of OpenMPI for Linux,
> mpicc/mpicxx are executables that read from driver files.
>
> Yet, I can't simply use ... CC=mpicc CXX=mpicxx ccmake ... because the
> intermediate executables for parsing and generating code must be built for
> serial execution.
>
> So what about some options to specify MPI compilers instead of or in
> addition to MPI_LIBRARY, etc.? I could probably work on the CMake scripts
> to implement this myself, but don't want to if there are major objections to
> that approach. Or, if someone is already planning on doing this, I'd love
> to know as it would save me _lots_ of time.
>
> Thanks,
> Sean
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>
More information about the ParaView
mailing list