It appears that MPI__VERSION is returning the version of the MPI
_standard_ that is supported by the chosen MPI. While I am sure this is
useful in some contexts, it’s actually not what I want/need for my project and
it is quite inconsistent with analogous versions such as
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-0000 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
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
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 had hoped to
capture such information in a cache file so that
