On Fri, Jul 20, 2012 at 12:58 AM, Cactus <rieman...@gmail.com> wrote: > >> We are probably ready to merge the MPIR-EXP branch into trunk but this >> will mean that there will be a (hopefully) short period during which the >> trunk won't build correctly. > > >> >> To minimise this period, it will be necessary to coordinate changes to the >> source code and to Windows Visual Studio build, the Windows command line >> build and the *nix/GCC builds. > > >> >> There are quite a large number of new C files involved and many new tests >> for the new FFT. I can provide information about the differences between the >> trunk and the MPIR-EXP branch if this will help in making these changes. > > >> >> I assume that Jason will need to look at the Windows command line build >> after the merge. Are you in a position to update this build if I now do >> this merge, Jason? Or is it likely to pick up the changes without any >> manual action on your part?
If you're interested, I have a modified command line build that worked with mpir-exp a while ago. I can update it after the merge. The batch files also support the selection of a specific version of VS or the MS SDK compilers. Case > > 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/-/dc-tkjET1dIJ. > > 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. -- 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.
