On 2018-07-09 12:48- Clune, Thomas L. (GSFC-6101) wrote:
[...]
Based upon conversations with colleagues in other institutions, the
most frustrating compiler is always the one you don’t do your
development with. Because of my clients, I mostly start with Intel
and then get frustrated
Mark and Juan,
Thanks! Between your two suggestions I was able to make something work.My
first attempt at using -DCMAKE_TOOLCHAIN_FILE resulted in some error messages
that I completely misinterpreted as needing to “re-teach” CMAKE about the
Intel compiler.A simple wrapper for the
> On Jul 9, 2018, at 1:04 AM, Alan W. Irwin wrote:
>
> On 2018-07-06 20:34- Clune, Thomas L. (GSFC-6101) wrote:
>
>> To use the Intel compiler, one must use an environment variable that
>> specifies the path to the license file. E.g.,
>>
>> export
ises many more issues as
> I need my project to be able to build with many different versions of the
> Intel compiler.
>
>
>
> Thanks in advance,
>
>
>
>- Tom
>
>
>
>
>
> *From: *Marc CHEVRIER
> *Date: *Saturday, July 7, 2018 at 1:49 AM
> *
On 2018-07-06 20:34- Clune, Thomas L. (GSFC-6101) wrote:
To use the Intel compiler, one must use an environment variable that specifies
the path to the license file. E.g.,
export INTEL_LICENSE_FILE=/usr/local/intel/license
Other commercial compilers use a very similar mechanism.I
You could user "cmake -E env " in combination with
https://cmake.org/cmake/help/v3.12/prop_gbl/RULE_LAUNCH_COMPILE.html and maybe
https://cmake.org/cmake/help/v3.12/prop_gbl/RULE_LAUNCH_LINK.html if needed.
Am 6. Juli 2018 22:34:04 MESZ schrieb "Clune, Thomas L. (GSFC-6101)"
:
>To use
mechanism to see that env
variable.
*From: *Stephen McDowell
*Date: *Saturday, July 7, 2018 at 2:25 AM
*To: *Marc CHEVRIER
*Cc: *"Clune, Thomas L. (GSFC-6101)" , CMake
MailingList
*Subject: *Re: [CMake] specifying path for license file for commercial
compiler?
I agree that a to
and therefore need a
separate mechanism to see that env variable.
From: Stephen McDowell
Date: Saturday, July 7, 2018 at 2:25 AM
To: Marc CHEVRIER
Cc: "Clune, Thomas L. (GSFC-6101)" , CMake MailingList
Subject: Re: [CMake] specifying path for license file for commercial compiler
From: Marc CHEVRIER
Date: Saturday, July 7, 2018 at 1:49 AM
To: "Clune, Thomas L. (GSFC-6101)"
Cc: CMake MailingList
Subject: Re: [CMake] specifying path for license file for commercial compiler?
May be using a toolchain file is more appropriate. See
https://cmake.org/cmake/help/v3
I agree that a toolchain file is more appropriate, noting that typically
modifying the environment variables is much more common for there's
compilers (particularly using environment modules).
However, since you've started clearly you would rather not set the
environment variables, there may be
May be using a toolchain file is more appropriate. See
https://cmake.org/cmake/help/v3.12/manual/cmake-toolchains.7.html
Le ven. 6 juil. 2018 à 22:59, Clune, Thomas L. (GSFC-6101) <
thomas.l.cl...@nasa.gov> a écrit :
> To use the Intel compiler, one must use an environment variable that
>
11 matches
Mail list logo
