<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Jay:</DIV>
<DIV> </DIV>
<DIV>Thanks for all your help.</DIV>
<DIV> </DIV>
<DIV>Actually, the last time I tried to install cm3, I used the 5.26 tarballs and tried to build, but ran into some compile errors. I'll try it again and report back the actual errors I get (if any).</DIV>
<DIV> </DIV>
<DIV>As for Microsoft Visual Studio, yes I'm familiar with setting it up.</DIV>
<DIV> </DIV>
<DIV>Are you saying that the cm3install program should no longer be used? I've used this in the past. The big issue I've run into is making sure to give old style 8.3 pathnames without spaces and to edit the cm3.cfg file to find all the libraries and stuff using paths without spaces. I've also set some environment vars, in particular the TEMP and TMP vars, to use paths without spaces.</DIV>
<DIV> </DIV>
<DIV>I will try to be very careful to document everything I do in great detail. Perhaps we can use this to give out a better recipe to folks on how to get cm3 working on Windows.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy<BR><BR>>>> Jay <jay.krell@cornell.edu> 11/29/2007 8:48 PM >>><BR>some more notes on the win32 system<BR><BR>> setup your C++ compiler/linker<BR><BR>You can/should "play dumb", skip that, and just run upgrade.<BR>See what errors you get.<BR>I tried to put in the right amount of up front sanity checking.<BR><BR>What you need in particular are<BR><BR>cl and link on the %PATH%.<BR> See, cminstall would have you specify full paths, my configuration uses %PATH%.<BR>If using VS2005 (8) or newer, mt on the path.<BR><BR>%LIB% is a semicolon delimited list of directories.<BR>That is a feature of the Microsoft linker.<BR>msvcrt.lib must be in one of them.<BR><BR>Any 32 bit version of Visual C++ -- 2.0, 4.0,, 4.1, 4.2, 5.0, 6.0, 7.0, 7.1, 8.0 -- should work.<BR>I have tested all of them some and many required small changes in one particular spot,<BR> that actually is only used by "maintainers" (C:\dev2\cm3\m3-win\import-libs\src\make-lib-1.cmd).<BR>I use 8.0 the most lately.<BR>I haven't done much with 9.0.<BR> <BR>Another thing, fairly redundant:<BR> <BR>C:\dev2\cm3\m3-win>more vcredist.txt<BR>On computers without Visual C++ 2005 or CLR 2.0 installed, download and run the setup for the Visual C++ runtime -- vcredist_x86.exe -- from either<BR> <BR>RTM (release to manufacturing):<BR> <A href="http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE">http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE</A><BR> <BR>or Service Pack 1:<BR> <A href="http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647">http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647</A><BR><BR>You can find those searching the web for vcredist, no real need to recort the URLs. That's about it.<BR><BR> - Jay<BR><BR></DIV>
<DIV>
<HR>
</DIV>
<DIV>Your smile counts. The more smiles you share, the more we donate. <A href="about:www.windowslive.com/smile?ocid=TXT_TAGLM_Wave2_oprsmilewlhmtagline" target=_new>Join in!</A> </DIV></BODY></HTML>