At the time I started almost two years ago, there was a much simpler wrapper or two, searching now yields a couple, but they are both for integers only and don't use deferred execution. At any rate, there isn't one that's officially part of MPIR, so I thought I'd make one.
Visual Studio does assume Windows; I haven't done any work in c# on Linux so that is indeed a very good question. Since my interop is written in C++/CLI, it's most likely a no-go for Linux, but according to http://tirania.org/blog/archive/2011/Dec-19.html Mono on Linux can already consume C++ directly so I'm guessing it can just use the native MPIR C++ interface. Mine was an effort to open MPIR to Windows .Net developers. On Linux, "makeinfo mpir.texi" runs without error, but "make pdf" gets me a "No rule to make target 'pdf'". However I can use "texi2dvi --pdf mpir.texi" to create a PDF; is that the same thing? I'm confused about diff vs. whole project. I was envisioning that my files, 95% of which are new and a handful existing MPIR files slightly modified, would become part of your repo just like Brian's VS builds now are. Then anyone downloading an MPIR release sources from mpir.org would have the option, if they like, to build my adapter and consume it. The other way this can work, and they can do it today, is if they clone my own fork, but I wonder if anyone in the world besides the readers of this thread knows about it. -- 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.
