On Wednesday 04 January 2012 09:19:01 Jason wrote: > > testing the command line builds under the directory win , this is > specifically with nehalem , vista64 , VS2008 > > 64bit static OK > 32bit static OK > 64bit shared OKish , make check fails the C++ tests > 32bit shared OKish , make check fails the C++ tests > > the C++ failures are all to do with unresolved symbols in istream and ostream > > This is the configure and make in the win directory , it should work with any > VS version from 2005 upwards and express versions as well > The compiler selection is the make sticking point and usually has to be > specified manually > > > There is also a command line build (configure/make) in the build.vc10 > directory , but this is just a command line wrappers around the build > solutions which support VS2010 and up only , I've not tested these and > perhaps we should delete them in favour of the new python solution > > I've not tested the python solution > > Besides docs , I believe we are good to go > > Jason > >
The doc changes in the info/pdf manual todo are I believe explain the windows command line build in the win directory explain the windows python build in the build.vc10 directory put the existing gui build instructions in the manual I think we should remove the command line (configure/make in build.vc10) driven build , its superceeded by the python build update for the new mpz_next_prime stuff I don't really know the syntax of the texi file , but I can do simple things , so the structure of the text must be simple :) Theres the usual notes, library versioning , changelog , credits todo Have I missed anything? Jason -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
