-----Original Message-----
From: Dann Corbit
Sent: Friday, October 26, 2012 2:36 AM
To: mpir-devel ; flint-devel ; sage-de...@googlegroups.com
Subject: RE: [mpir-devel] MPIR 2.6.0 beta released
[snip detail]
I was able to build the dll and static libraries.
However, when I try to build the mpir-tests project, I get many errors like
this:
120>Time Elapsed 00:00:00
119>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(103,5): error
MSB3073: The command "..\check_config x64 Release
119>C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(103,5): error
MSB3073: :VCEnd" exited with code -1.
Perhaps it is due to my path. I install mpir into a folder named math. For
instance:
c:\math\mpir-2.6.0\build.vc10
there is a batch file named check_config.bat in the mpir-tests folder:
Directory of c:\math\mpir-2.6.0\build.vc10\mpir-tests
10/03/2012 01:07 PM 1,176 check_config.bat
=====================
Hi Dann,
There are a couple of points that you should bear in mind when building MPIR
on Windows with Visual Studio.
When building and testing, the tests are run on the latest version of MPIR
that has been built, which means that if you build several versions of MPIR
you need to interleave the builds and the tests - build v1, test v1, build
v2, test v2, ... The same applies to the tuning as well, although I should
mention that the tuning is very unreliable on Windows.
The second point is that Visual Studio builds are in one of four
configurations x64/release, x64/debug, win32/release and win32/debug. When
you build MPIR you need to set which of the four configurations you want to
build. When you build the tests, it is very important that you set the
build configuration for the tests to be the same one that you used in the
MPIR build. The batch file check_config.bat will test that you have done
this correctly and will prevent the tests being built if you have set the
incorrect configuration.
I realise it would be better for me to set this automatically but I have
avoided getting into Visual Studio build automation at this level of detail
so the batch file configuration check was the easiest thing I could do to
prevent errors.
So I think you have built one configuration of MPIR but have then used a
different one when you tried to build the tests.
Case has suggested that you should change the root directory from MPIR-2.6.0
to MPIR. That will do no harm but it is not necessary to build MPIR.
But it _is_ necessary if you build libraries or applications (MPFR, MPC,
GMP-ECM, ...) that depend on MPIR and use my Visual Studio build files to
build these libraries/applications.
I hope this helps. If you still see failures please do not hesitate to seek
further help.
Brian
--
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.
