On Jun 26, 2005, at 11:30 PM, Cheng, Kevin wrote:
>> 1. If one had an existing project, say a GTK or QT application with
> Makefile and everything. If one wanted to incorporate MPI into this
> project, one would just replace (in the Makefile) the 'GCC = gcc'
> to 'GCC = mpicc', 'GXX = g++' to 'GXX = mpicxx', and also maybe
> include some MPI lib paths to the INCPATHs? Is this how one can
> convert normal projects into projects incorporating MPI calls?
That should work - mpicc is just a front end wrapper - so give it a try!
The mpicc script also sets up all the appropriate include and library
paths.
>> 2. If one had an existing C MPI program. What would be the side-
> effects of using the mpicxx to compile C code? Is it strict for one
> to use the MPI:: classes opposed to MPI_ C functions.. when force
> compiling under C++?
Either will do. The MPI-1 standard contained only C and FORTRAN
bindings, while the MPI-2 standard included the C++ bindings. If you
only have access to an MPI-1 implementation (eg. MPICH v1.X) then you
may end up having to use the C bindings instead of C++.
Good luck,
-bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.beowulf.org/pipermail/beowulf/attachments/20050628/56bbc625/attachment.html>