On 28/04/2015 20:22, Dann Corbit wrote:
> When I say
> "the bug still exists"
> I refer to the build problem with Visual Studio 2013, I do not know
about the failed test with more recent versions because I did not try it.
Hi Dann,
I am not sure what bug you are talking about here since, as far as I
know, there is no bug in the Visual Studio build provided you do the
build as intended. That is build MPIR in config1, test MPIR in config1,
build MPIR in config2, test MPIR in config2, ...
If you want to build the various Windows configurations of the library
before running the tests, you can do this but you then have to edit the
file:
mpir\build.vc12\output_params.bat
to indicate which MPIR library you wish to test.
An example of the content of this file is:
(set libr=lib)
(set plat=x64)
(set conf=Release)
This file is written when MPIR is built so that the subsequent test
build knows which library to test.
But there is nothing to stop you editing this file so that the test
build picks up the MPIR library configuration that you want to test.
The format should be fairly obvious:
(set libr=<lib|dll>)
(set plat=<Win32|x64>)
(set conf=<Release|Debug>)
where the choices are the alternatives within the <>'s.
I have just rebuilt the library from a fresh version cloned from the
MPIR repsository using the lib/x64/Release configuration and all tests pass.
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 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.
