Hi Leif, I thought the mpirxx.h files should be generated/updated when building the mpir library. I assumed that because I got some other errors when using the default tarball/zip file, thanks for clarifying that.
Brian already commented something else that is related to this issues, I will follow up that post. Thanks much. Guillermo. On Friday, May 30, 2014 5:18:55 AM UTC-7, leif wrote: > > Guillermo Ramírez wrote: > > Hi, > > > > I followed the instructions on the MPIR 2.7.0 manual on how to build > > MPIR with Microsoft Visual Studio. I am using VS2013 and a x64 system > > with i5 core. I also did the suggested testing for > > MPIR mpir/build.vc12/mpir-tests/run-tests.py and it worked. > > > > However, the header file mpirxx.h is not updated when bulding the c or > > c++ libraries. The files mpir.h, mpir.lib, mpir.pdb, mpirxx.lib and > > mpirxx.pdb are succesfully generated. > > I'm not entirely sure whether I understand your problem (if it is one). > > In contrast to mpir.h/gmp.h, the file mpirxx.h doesn't get generated > during a build, but is only shipped with the tarball/zip. (It includes > mpir.h/gmp.h though.) > > > -leif > > > I am using the release and x64 > > options to build the mpir libraries for the lib_mpir_core2 and > > lib_mpir_cxx projects. > > > > Is it ok that I choose the x64 system? I know some people have had > > issues when building 64 bits libraries. Is there any missing steps in > > the MPIR manual? Hopefully you can give me some insight on this. > > > > Thanks. > > Guillermo. > > -- > () The ASCII Ribbon Campaign > /\ Help Cure HTML E-Mail > -- 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.
