I'm writing an MPZ language binding that should potentially be available for different Windows/Linux architectures.
What would be the best way to provide the binding to end users? E. g. for Windows (both 32 and 64 bit), compile the binding against the DLL interface, and supply a base (not optimized) MPIR DLL. Then, optionally supply MPIR DLL's optimized for some specific architectures, and let the user copy/rename the DLL's based on his current processor? Does a binding which was compiled against a specific gmp.h and mpir.lib, allow to be run against different (base or optimized) mpir.dll's without recompiling? Same with new MPIR vrsions: would compiling a new MPIR DLL and replacing the older version be sufficient? Is there a way for a user to easily figure out, if he should (e. g.) stick with the base mpir.dll, or whether he could safely replace it with a (renamed) mpir-nehalem.dll or mpir-sandybridge.dll? Is there a way for the language binding to check whether it is being supplied an acceptable mpir.dll (short of just crashing)? Or, nothing from above, but compile against the .lib interface? Thanks! -- 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.
