While I use mpir I get the following warnings: r:\include\gmpxx.h(118) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(164) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(215) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(288) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(332) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(340) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(377) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(424) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(431) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(459) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(544) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(592) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(628) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(696) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(741) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(783) : warning C4146: unary minus operator applied to unsigned type, result still unsigned r:\include\gmpxx.h(793) : warning C4146: unary minus operator applied to unsigned type, result still unsigned
These are all places where the following code appears: -static_cast<mpir_ui> where mpir_ui is 'unsigned long' do you have any idea about the purpose of this code? I assume mpir_ui stands for unsigned int. luni, 14 iulie 2014, 00:08:34 UTC+3, Cactus a scris: > > On 13/07/2014 19:36, Oneț Cristian wrote: > > >> The build of the MPIR C++ library has to be performed after one of the > >> main MPIR libraries has been built. As you say, this could be avoided > >> by adding a prebuild step to the C++ library project. > > > > Could you fix this for the next release? I could send you a patch with > the > prebuild event. If cxx needs to be compiled after the main libraries this > dependency should be added to the solution. > > Although adding the prebuild step works, adding it to the C++ library > build is not a good idea as it runs steps that will only run correctly > when used with the main MPIR library builds (i.e mpir.lib and mpir.dll). > > And the problem with adding a build dependency is that the C++ project > would have to be made dependent on every MPIR library that can be built > since we don't know which one the user will choose to build first. > > This would mean that building the C++ library would trigger all the main > library builds and, since they all output into mpir/lib or mpir/dll, all > except the last would be overwritten. > > I must admit that I didn't anticipate that anyone would try to build the > C++ library before MPIR itself but the need to build MPIR first is set > out in the readme.txt file. > > >> This second issue is caused by an error on my part in not updating the > >> tuning of the Windows win32 builds. If the file: > > > Mpir is used by the KDE on Windows project (http://windows.kde.org/) > as a replacement for gmp. I'm happy to volunteer as a tester of the > library since we use it regularly to build KMyMoney > (http://www.kmymoney.org/) > on Windows. I have to say that Windows support kept improving since the > 2.3.0 > release that we first tried. > > I am not sure but I suspect that more than just testing is likely to be > needed as the tuning files for the win32 code (i.e. gmp-mparam.h) have > not been maintained since Jason MMoxham passed away. But we certainly > need help for the Windows win32 assembler builds as I simply don't have > the time to maintain them (the generic win32 build should be fine). > > 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.
