[MPICH] Still having problems after switching to Visual Studio.net C++

[David Ashton]

The binary distribution of MPICH2 does not contain the debug versions of the
libraries.  If you don't want to step through the MPICH2 source code then
you can link with mpi.lib instead of mpid.lib.  If you do want to link with
mpid.lib then you will have to build MPICH2 from the source distribution.
After following the steps in the readme.windows file you will have the debug
libraries in the lib directory.  You can link with mpid.lib and you will
have to distribute mpich2mpid.dll and mpich2d.dll to all the nodes.  You
will also have to distribute msvcrtd.dll to all the nodes since Microsoft
does not distribute the debug dlls either.

-David Ashton

-----Original Message-----
From: owner-mpich-discuss at mcs.anl.gov
[mailto:owner-mpich-discuss at mcs.anl.gov] On Behalf Of peter_raeth at juno.com
Sent: Friday, November 11, 2005 10:24 AM
To: obie at hiram.edu
Cc: mpich-discuss at mcs.anl.gov
Subject: Re: [MPICH] Still having problems after switching to Visual
Studio.net C++

Using the cpi VS.NET project distributed with MPICH2 source, there is an
attempt to link with mpid.lib. That file is nowhere on our system, after
installing the source and the WIN binary distributions.

At issue with mpi.lib is that we want to build a debug version of our code.
We started with the sample cpi project as a means of seeing a correct build,
going from source to cluster runs.

Is it necessary to go through the MPICH2 build process to get mpid.lib
created?

Thank you for any insights you can offer.