-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License? MPFR C++ is GPL #9
Comments
Hi @cxw42 ,
With some research and without previous intent to the opposite, @cxw42 , your point is valid, however it was not without conversing and advice from the author, so it was not with malicious intent. @advanpix , what are your thoughts here and what would you like to happen? Thank you for all of your input! -Mark |
NOTE We also worked closely with Dr John Burkhardt of the University of South Florida on his porting of QUADPACK back in 2012-2014, but I an am failing to locate/contact him at this point after some web searching. |
As the author of MPFR C++ I confirm that there is no license conflicts, as I personally agreed for MPFR C++ to be distributed with Eigen and this library under MPL. The only exception is commercial usage of MPFR C++: this requires special commercial license. I am not sure if this plays well with the intention of the authors of the library. |
@advanpix Thank you very much for the response and confirmation! Just to make sure:
Am I understanding you correctly? Much appreciated! |
I agree with your choice of the MPL license. However, I see from http://www.holoborodko.com/pavel/mpfr/#license that MPFR C++ is GPL (apparently GPL 3), unless you make other arrangements with the author. I am not a lawyer, but my impression was that code linking with GPL had to be licensed GPL or compatible. Do you have any information about MPL vs. GPL?
Related to #7, is it possible to build without MPFR C++? I see that
NumericalIntegration.h
unconditionally includes<unsupported/Eigen/MPRealSupport>
--- could that be removed for a non-MPFRC++ version?The text was updated successfully, but these errors were encountered: