<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0">
<TITLE>RE: [mpich-discuss] Build MPICH2-1.0.8 for Windows in VS 2005</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2> Hi,<BR>
You should look into the batch file, makewindist.bat, to see the right configurations to use to build MPICH2. If you are only developing MPI applications (and not modifying MPICH2 code) you don't need to compile MPICH2 on windows - the MPICH2 sdk can be installed using the MSI installer available at the MPICH2 downloads page (<A HREF="http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=downloads">http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=downloads</A>).<BR>
Let us know if you need help.<BR>
<BR>
(PS: Most of the warnings that you see would be related to not using windows specific secure versions of string manipulation functions. Let us know if you are concerned about any particular warning message during the compilation.)<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
-----Original Message-----<BR>
From: mpich-discuss-bounces@mcs.anl.gov [<A HREF="mailto:mpich-discuss-bounces@mcs.anl.gov">mailto:mpich-discuss-bounces@mcs.anl.gov</A>] On Behalf Of Hiatt, Dave M<BR>
Sent: Friday, November 14, 2008 3:39 PM<BR>
To: mpich-discuss@mcs.anl.gov<BR>
Subject: [mpich-discuss] Build MPICH2-1.0.8 for Windows in VS 2005<BR>
<BR>
I read the documentation and got the impression that it was possible to build MPICH2 using the mpichs.sln<BR>
<BR>
I'm using VS2005, and Perl. After running winconfigure.wsf with the --remove-fortran --cleancode options; I started VS and opened the solution. 21 projects loaded.<BR>
<BR>
Of those a number built with no problem. A significant group of others had errors, that in general always had to do with creating a proper path to a missing header file location. In addition many of the projects had numerous warnings. I mention this because I believe I read that the system should build error and warning free. So I found this more than a little disconcerting and began to wonder if it was indeed supported to build directly from Windows.<BR>
<BR>
But when building the project mpich2 I ran into a more significant problem. Prior to this I had two cases of linking failing because paths to a required "lib" was not correct or added. In each case I could do a search with Windows explored and find the needed lib. However in this case, no lib named as required was found. The case is, mpich2 project is looking for "sockd.lib". This lib is not mentioned that I can find anywhere. There is a "sockpd.lib" built, but not a sockd.lib.<BR>
<BR>
Is anyone else building 2-1.0.8 directly in Visual Studio, and in particular VS2005? If so, have you seen this issue as well as the warnings and other mapping problems in the projects, or have I simply missed something along the way.<BR>
<BR>
Any ideas would be greatly appreciated.<BR>
<BR>
Dave<BR>
<BR>
If you lived here you'd be home by now<BR>
Dave Hiatt<BR>
Manager, Market Risk Systems Integration CitiMortgage, Inc.<BR>
1000 Technology Dr.<BR>
Third Floor East, M.S. 55<BR>
O'Fallon, MO 63368-2240<BR>
<BR>
Phone: 636-261-1408<BR>
Mobile: 314-452-9165<BR>
FAX: 636-261-1312<BR>
Email: Dave.M.Hiatt@citigroup.com<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>