I would prefer not to document the python build in this release as it is only experimental at the moment. The definitive version is the one I am working on in the mpir-exp directory in SVN and I don't guarantee that the version in trunk will work..
For the next release I am working on a new Windows version in the experimental branch in the SVN (mpir-exp). This has now had a reasonable amount of testing on Windows and seems to work fine with no obvious problems. Its main feature is the introduction of two new integer types gmp_ui and gmp_si (maybe I should call them mpir_ui and mpir_si?) that are then used for all inputs/outputs in the GMP ui/si functions. This has already proved useful in avoiding the 32-bit long problems on Windows x64. The only issue is to encourage people to use gmp_printf rather than printf as this has the %M output format coded to automatically output the mp_limb_t type correctly. But this now _really_ needs to be tested on Linux in order to ensure that I have not messed anything up on non-Windows systems. So with the new FFT, the new Visual Studio build system, the possible removal of the "32-bit long" issue on WIndows x64, and, if Jason can do it, a new Windows friendly tuning system, the next release promises to be a big step forward, especially so on Windows. Brian -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To view this discussion on the web visit https://groups.google.com/d/msg/mpir-devel/-/3ZHv8g8-L8wJ. 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.
