Closed sunoru closed 4 years ago
I just added a .travis.yml
using julia-icc-travis, and it works well now.
I think we need to be a bit careful here about licensing: according to the EULA:
NOTWITHSTANDING ANYTHING TO THE CONTRARY ELSEWHERE IN THIS AGREEMENT, YOU MAY USE THE MATERIALS ONLY FOR EVALUATION PURPOSES AND ONLY FOR THE TERM OF THE EVALUATION, YOU MAY NOT DISTRIBUTE ANY PORTION OF THE MATERIALS, AND THE APPLICATION AND/OR PRODUCT DEVELOPED BY YOU MAY ONLY BE USED FOR EVALUATION PURPOSES AND ONLY FOR THE TERM OF THE EVALUATION.
which I'm not sure this would be adhering to. Perhaps the community license version would be better, though ideally we would get some sort of confirmation from Intel.
I agree, and it's easy to use community license in the scripts. However the problem is that the license key should be stored in the account that owns the project, so perhaps the official julia group rather than me should apply for a license?
Doesn't MKL have a license for open source usage that should not be for evaluation?
Cc @kpamnany
@ViralBShah IIRC It requires an application and then you just get a serial number.
Not sure if this has proceeded from here, but here is a link to register for an Open Source license for Intel's MKL. As far as I understand the EULA, this is the correct license for use on Travis/AppVeyor. Apologies if this has already been set up.
The downside is the open source license is only available for Linux. There is a Community license available for Windows, Linux and OS X but there is not a lot of information available about where the distinction lies between open source and community. Might be worth contacting Intel?
I think the community one is the best bet. The conditions on the open source one are quite restrictive (see https://github.com/travis-ci/travis-ci/issues/4604).
I think this PR is very outdated at this point.
5