-----Original Message-----
From: Brian Gladman
In my view, those who need such hybrid build capabilities should (a)
explain why they can't use MSVC to build MPIR, and (b) put in the effort
to support such builds if they really need them.
Yeah, that's fair enough.
It sounds much like the "forbid it" option I mentioned - though, more
accurately, it's probably just a "we don't support the practice" policy.
If that's not already documented somewhere, maybe it should be - something
like:
###############################
The practice of using a MinGW-built mpir library with a Microsoft compiler
is currently not supported, and the mpir developers discourage such
practice.
However, if we receive well tested documentation on the steps that need to
be taken when using a MinGW-built mpir library with a Microsoft compiler, we
will happily reproduce that documentation here.
Until then (and even after that), the responsibility for such a practice is
your own.
###############################
Or, if the mpir developers want to wipe their hands completely clean of this
matter:
###############################
The practice of using a MinGW-built mpir library with a Microsoft compiler
is currently not supported, and the mpir developers discourage it.
The responsibility for such a practice is your own.
###############################
Cheers,
Rob
--
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.
