That does look useful! For the architecture parameter, the two common scenarios are:
1. I'm going to link to a program which I'm then going to ship as a binary. I need something that will work correctly on every x64 CPU, and should preferably be optimised according to the distribution of machines that exists today or is projected to exist over the next few years. 2. I'm compiling stuff purely to run on my own machine. I don't know exactly what variant of CPU it has, but would by all means like the code to be optimised for my CPU, whatever that happens to be. What should be specified for the architecture parameter in each case? On Tue, Jul 21, 2015 at 11:09 PM, Brian Gladman <b...@gladman.plus.com> wrote: > On 21/07/2015 14:13, Russell Wallace wrote: > > It does exist, and the build now works with no errors. > > I have added a commandline build for Visual Studio 2015 to my MPIR > GITHUB repository at: > > https://github.com/BrianGladman/mpir > > The file is msbuild.bat in the build.vc14 directory (it uses MSBUILD to > do the hard work). > > This is used by opening a command prompt in the build.vc14 directory and > then entering the command: > > > msbuild <architecture> <lib|dll> <Win32|x64> <Release|Debug> > > where <architecture> is the version to be built and the <a|b> terms are > alternatives that set the library type (static library or dll), the > platform (Win32 or x64) and the configuration (Release or Debug). > > For example: > > > msbuild core2 lib x64 release > > will build the core2 static library version of MPIR for x64 in release > mode, and: > > > msbuild sandybridge_ivybridge dll x64 debug > > will build the sandybridge_ivybridge DLL version of MPIR for x64 in > debug mode. > > Hopefully this will provide a substitute for the removed command-line > build. I have tried it successfully on several builds but it is likely > to contain bugs. Note also that if you wish to try it, you will need to > update your postbuild.bat file (in build.vc14) to that in my GITHUB MPIR > repository. > > I would appreciate feedback on this as it will be very easy to add to > MPIR if it is useful. This is because there is almost no maintenance > cost as all the hard work is done by the existing Visual Studio builds. > > 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 mpir-devel+unsubscr...@googlegroups.com. > To post to this group, send email to mpir-devel@googlegroups.com. > 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 mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
