I am currently evaluating both the Linux and Windows versions of Parallel Studio XE for my company. One important issue that I haven't yet been able to locate an answer for is in regards to licensing of the Intel OpenMP library (as distributed with Parallel Studio XE).
More specifically, The linux version of the Intel compiler has an option `-static-intel` which among other things, can statically compile in the Intel OpenMP library `libiomp5`. My question about this OpenMP library is about its licensing (more specifically when statically compiled into a program).
Jumping in as I see no answer was provided within the expected time period. As a retired Intel employee, I can't provide authoritative answer, but maybe help you know what to look for.
Support for static libiomp5 was withdrawn several releases back. Perhaps you are talking about a past release. static-intel now is ignored in respect of this library (and 1 or 2 others).
If you have a developer license (not a demo, beta, or student license) you are permitted to distribute the shared objects required by your application, and the linked executable including available static libraries (with possible exceptions if you link IMSL). This should be covered in the licenses installed with your compiler. Among the options is to provide the full distributable shared library installer associated with your Intel compiler (available alongside the compiler at the download site registrationcenter.intel.com).
If you have in mind acknowledging matters pertaining to linux such as gnu library run time licensing, there isn't any counterpart with Intel Windows compilers.
I'm so terribly sorry about the long delay.
I am not a lawyer, so I had to send your question to Legal. My intention was to wait for their response before replying here, to avoid giving you a non-answer, but it's taking much longer than I thought.
Hopefully we'll have an answer for you soon.
Thank you both for your responses and please do follow up when you get a response from legal.
My evaluation period for Parallel Studio XE ends this Friday however, I will still have some time to update the internal report that I am preparing (for management and purchasing). So even if it's a little after the fact, getting back to me with that response is still important.
Thank you for your questions. The following information may be helpful to you (as of this writing):
The Intel® OpenMP* Runtime Library is dual licensed under (1) an Intel proprietary End User License Agreement (EULA), and (2) under the BSD 3-Clause License (see: https://www.openmprtl.org/faq/10). If you are using the Intel® Parallel Studio XE for Linux (which is licensed under the Intel EULA), you will need to license the library under the BSD 3-Clause License. If you are using Intel® Parallel Studio XE for Windows* (also licensed under the Intel EULA), you will license the library under the Intel EULA.
For the Intel EULA (see https://software.intel.com/en-us/articles/end-user-license-agreement):
Attribution requirements are set forth in Section 3.B which states the following: “If Your Product is a software development library, then attribution (if any), as specified in the product release notes of the corresponding Materials shall be displayed prominently in Your Product’s associated documentation and on the web site (if any) for Your Product.” The current release notes for Intel® Parallel Studio XE can be found here: https://software.intel.com/en-us/articles/intel-parallel-studio-xe-2017-release-notes.
The Intel OpenMP Runtime Library is listed in the credist.txt and fredist.txt files so it is a “Redistributable” under the Intel EULA (see notes at: https://www.openmprtl.org/faq/10). The distribution requirements for Redistributables are set forth in the Intel EULA’s license grant in Sections 2.1.A(4), 2.1.B(3) as well as in the restrictions set forth in Section 3.F .
For the BSD 3-Clause License:
Attribution and distribution requirements for the library are set forth in the BSD 3-Clause License (see: https://opensource.org/licenses/BSD-3-Clause).
Also, we intend to update the Q&A site to make this information clearer.