My condolences regarding Jason Moxham. But you're right about vsyasm. The documentation said you had to do various things to hack the visual studio configuration, but when I tried your suggestion of just moving vsyasm.exe into the bin directory, it worked. That does require an administrator prompt, but nonetheless I think it's within the bounds of what I can reasonably ask users to do.
I did get a couple of error messages that I think are a separate issue. I'll post those in a separate topic. There was a mention at some point of the use of clang to build mpir. What procedure do you use for this? (I have a program that will allow clang to be directly substituted for Microsoft C++, but I'm interested in what you've been using.) On Tue, Jul 21, 2015 at 11:06 AM, Brian Gladman <[email protected]> wrote: > On 21/07/2015 10:29, Russell Wallace wrote: > > 2.6.0 used to be quite straightforward to build on Windows; despite the > > references in the documentation to vsyasm, the build procedure actually > > worked fine with plain yasm, which could be placed anywhere in your > > path. Unfortunately 2.6.0 doesn't build with Visual C++ 2015. > > > > 2.7.0 does seem to be compatible with Visual C++ 2015, but unfortunately > > the build batch files seem to be gone, and the new msbuild procedure > > doesn't work with yasm. Presumably I could hack vsyasm Into Visual > > Studio with enough effort, but that doesn't seem to be a repeatable > > procedure, and exceeds the threshold of work that can be expected of > > each user trying to build a program that depends on mpir. > > Hi Russell, > > Unfortunately the batch file build on Windows was maintained by Jason > Moxham who sadly passed away in 2012. In consequence it had not been > maintained since then and could not therefore be used to build MPIR 2.7.0. > > I am puzzled by the problems you have (or foresee) with vsyasm. It > should be no more difficult to use vsyasm with Visual Studio than it is > to use yasm. All you have to do for Visual Studio 2015 is to add > vsyasm.exe to the Visual C++ binary directory at: > > C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin > > after which the Visual Studio builds should work 'out of the box'. > > There was a problem with the vsyasm.exe provided on the yasm site but I > believe that Peter Johnson has now solved this. If it still fails, I > will be happy to send you a version that I know works. > > Since you have to put yasm somewhere where Visual Studio can find it, > how is doing this for vsyasm any different? > > Can you explain in what way the current Visual Studio builds are not > repeatable? > > Maybe I can help you to set up an environment in which these builds will > work for you. > > > Is there a way to bring back the ability to use plain yasm, and thus or > > otherwise obtain a repeatable procedure for building mpir? > > This could be done but it would need a volunteer to update them for MPIR > 2.7.0 and then to maintain them for the future. > > best regards > > Brian > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/mpir-devel. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
