Whoops, here are the compiler logs! Can't seem to figure out how to edit my last post.
1>------ Rebuild All started: Project: add-test-lib, Configuration: Release x64 ------ 1>EXEC : error : static library tests need 'mpirxx.lib' 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(123,5): error MSB3073: The command "cd ..\..\..\build.vc 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(123,5): error MSB3073: check_config x64 Release 15 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(123,5): error MSB3073: :VCEnd" exited with code -1. 1>Done building project "add-test-lib.vcxproj" -- FAILED. ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ========== 1>------ Rebuild All started: Project: mpz.addsub, Configuration: Release x64 ------ 1>EXEC : error : static library tests need 'mpirxx.lib' 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(123,5): error MSB3073: The command "cd ..\..\..\build.vc 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(123,5): error MSB3073: check_config x64 Release 15 1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(123,5): error MSB3073: :VCEnd" exited with code -1. 1>Done building project "mpz.addsub.vcxproj" -- FAILED. ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ========== On Fri, Aug 17, 2018 at 9:47 PM, UZRNW SDRXG <sdvuis2341dwvsw...@gmail.com> wrote: > I have been trying it all day. I can do several different things so far, > but none lead to success. I can successfully compile a mpir.lib Release/x64 > and incorporate it into another C project. However compiling that project > complains of not being able to open LIBCMT.LIB. LIBCMT is a VStudio lib and > not used by my other C compiler at all. I am not sure why it's trying to > use it either. > > If I try to compile any of the \mpir-3.0.0\build.vc15\tune.sln examples > they all fail instantly with the same non-helpful error. > > On Fri, Aug 17, 2018 at 5:13 PM, Brian Gladman <b...@gladman.plus.com> > wrote: > >> On 17/08/2018 21:59, Brett wrote: >> >> > Hello, I really would like to use MPIR but I cannot after 1+ month of >> trying for 200+ hours get anything to do anything. I know in Unix it's >> typical to release source code, but on Windows nobody does it that way. >> >> Hi Brett, >> >> I'm sorry that you have had issues in obtaining a suitable windows >> binary of MPIR. I wish that you had asked for help here before doing >> all that work since I feel sure that we could have steered you in the >> right direction. >> >> Please just compile your binary and upload the single .exe, .dll, or >> .lib to the internet. Unlike Unix, Linux, and Mac, there is only one >> version of Windows, so you only need to upload one binary file! It's a >> lot easier on Windows! So please understand compiling other peoples' >> source code on Windows in not standard, and as such you & us will only >> ever have problems. We need to set up our computers to be exactly like >> your computers in order for any source code to be worth anything. >> >> The Windows build system for MPIR uses Microsoft Visual Studio for which >> a free version is available. The reason we don't offer binaries is that >> there would have to be a lot of them since most users of MPIR want very >> high speed and this means that the code has to be built for the specific >> Intel processor on which a user wishes to run it. >> >> But the Visual Studio build system is reasonably easy to use and a lot >> of people are using it without difficulty so we should be able to guide >> you through the process if you have run into trouble using it. >> >> I know from Unix and Linux you guys obfuscate your OS and installation >> methods in order to make it difficult and cool to use Linux. But >> everyone else just wants to download 1 binary file and run it like you >> know.. a normal person. You know how there's just 1 icon on my desktop >> for Internet, and 1 icon for E-Mail, and 1 icon for Facebook. You need >> to make 1 icon for MPIR! There is no need to have a .zip file with 4,172 >> files in it! Windows isn't like Linux, it's not hard to use! Windows can >> just have 1 file! >> >> As Bill has said we don't have the bandwidth to host the binaries as you >> suggest. But you are right that the current distribution approach is >> one in which we put both the Linux and the Windows build into the same >> distribution so each carries the unnecessary overhead of the other. I >> have a feeling that we should now offer the Linux/GCC and Windows/Visual >> Studio builds as two separate distributions as this would greatly reduce >> the size of the Windows distribution in particular. >> >> If you are willing to try the Visual Studio build for MPIR, I feel sure >> that I will be able to guide you through it (I am the developer and >> maintainer of the build system on Windows). >> >> with my regards >> >> Brian Gladman >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "mpir-devel" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/to >> pic/mpir-devel/HAHjnlowYxg/unsubscribe. >> To unsubscribe from this group and all its topics, 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 https://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 https://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
