<html><body>
<DIV>I worked on the walton branch. It may be broken at the moment. I did a bit of the porting work...since then Tim merged it into the main branch keeping some and discarding other work I added. It was the right thing to do. Some was "real", some was "experimental"...</DIV>
<DIV> </DIV>
<DIV>He did the right thing for a variety of reasons, but I haven't verified that the trunk branch builds cleanly with MSVC yet. That is on my list of things to do "real soon now" in my "ample free time". :-/ </DIV>
<DIV> </DIV>
<DIV>I think we need another iteration or two to get it cleanly and safely building with MSVC...and Tim and I both are pretty busy. </DIV>
<DIV> </DIV>
<DIV>It was built using MSVC8 (VS2005)...I believe but have not verified that an 'express' version can be downloaded from Micro$oft. </DIV>
<DIV> </DIV>
<DIV>Good luck!</DIV>
<DIV>Philip</DIV>
<DIV>> Date: Thu, 29 Jun 2006 12:34:41 EDT <BR>> From: WoelliUSM@aol.com <BR>[snip]</DIV>
<DIV>> Dear all, <BR>> <BR>> I downloaded the latest FlopC++-version from svn-repository to build it <BR>> under VisualC++. To build a flopc.lib, I used the "walton"-directory and the <BR>> "trunk"-directory. The version from the "walton"-directory had only errors <BR>> concerning the mp_constraint.hpp-file. Is this still a problem because of the <BR>> "wrong" version offered in the repository? Or should the version in the <BR>> "walton"-directory work? If so, does someone have a working version of FlopC++ <BR>> under <BR>> Visual C++ and please tell me, what I have to do? <BR>> <BR>> Thanks in advance! <BR>> <BR>[snip]</DIV></body></html>