On 24/11/2015 09:38, SeVlaT wrote: > I have all of them. > > What exactly should be tested?
That is a very good quation! With 27+ varients each combined with both <Release|Debug> and <LIB|DLL>, it is not practical to build and run the tests on Windows even for one version of Visual Studio without further build automation (which I have thought about). > My variant: > 1. Set usecpp=True to generate cxx project > 2. Run mpirconfig four times and pass him all numbers 1-26 Do you mean here for four versions of Visual Studio? > 3. Ensure that all solutions are buildable Under normal circumstances, I only test the with the current version of Visual Studio (2015 now). But with all the recent changes I am going to ensure that Visual Studio versions 2012, 2013 and 2015 are all working. I don't however test all variants. Unless I expect a specific problem, I only build and run the tests for the GC versions and for my current processor (sandybridge_ivybridge). I don't do any testing of win32 builds other than GC as I consider all these builds obsolescent. At the moment the vc14 version is fairly complete and should be fully working. Yesterday, I completed the corrections needed for the vc12 version but I haven't yet committed them. I hope to complete this later today. When I have finished vc12 I will move on to VC11. I do not intend to offer support for earlier versions (Visual Studio 2010 and earlier). 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.
